I am writing a stylesheet to use with my Compiled Help files. It looks like CSS2 generally works, but I'm not sure about CSS selectors like > and +.
Is the CHM format equivalent to, say, IE 7?
fwiw, I am authoring on Windows 7 and IE9 is installed.
On Windows Vista and later (I tested 7, 8, and 8.1), the HTML Help Viewer uses IE 7, even if you have a more recent version of Internet Explorer installed, and even if Windows itself comes bundled with a more recent version of Internet Explorer.
On Windows XP and prior, if the user has IE 7 or prior installed, then the HTML Help Viewer uses whichever version of IE the user has installed. If the user has IE 8 installed, then the HTML Help Viewer will use the IE 7 engine, even if the user never installed IE 7. IE 9 and later cannot be installed on Windows XP or prior.
So it seems HTML Help will be fovever stuck with IE 7.
Here's a small CHM file that you can use to test this:
http://download.jgsoft.com/helpscribble/UserAgent.chm
(If the right hand pane of the HTML Help Viewer shows "navigation canceled" or a similar error, you need to right-click the downloaded CHM in Windows Explorer, select Properties, and then click the Unblock button.)
The HTML Help Viewer uses the layout engine components of Microsoft Internet Explorer (Shdocvw.dll hosting Mshtml.dll) to display Help topics.
http://msdn.microsoft.com/en-us/library/aa189109%28v=office.10%29.aspx
Which means: CSS version support is determined by which IE version is installed.
Related
I have an application that is using GWT 2.0.4 and running fine on IE8 browser. When opened in IE11, it is giving blank page with error message given below.
com.google.gwt.core.client.JavaScriptException : (TypeError) : Object doesn’t support property or method ‘attachEvent’
The exception was thrown because “attachEvent” is a deprecated function used in older versions of Internet Explorer. IE11 uses “addEventListener” method instead of “attachEvent”.
The user.agent value was set to "ie6" so i changed it to "gecko1_8". After changing user agent it opens the application but the data in table(GWT-ext GridPanel) is getting overlapped over one another, scrollbars are missing and the alignment of menu bar is changed.
It is working fine after enabling the compatibility mode. What is the proper workaround to run my app in IE11 ? Do i need to upgrade GWT and if yes then to which version supports IE11? I don't have to use "X-UA-Compatible=IE8" meta tag....Please help
As with anything on the Web, you should always try to run the latest version, because everything changes around your application. 2.0.4 is 5 years old already!
So yes, upgrade to the latest version of GWT (2.7.0 as of today), and when the next version will come (2.8, in a few weeks) try to upgrade as well.
As a workaround, because it works in IE8, you could probably ask IE11 to emulate it using an X-UA-Compatible with value IE=EmulateIE8. But that's only a temporary workaround, as the next version (Edge, coming in Windows 10 to replace IE) will no longer support X-UA-Compatible (except in the Intranet zone). See the warning at the top of the X-UA-Compatible doc and this announcement by Mirosoft. The real solution is to stay up-to-date with GWT versions, just like you stay up-to-date with browser versions.
I note that I cannot be launched on web IE 11 ..
I know that the useragent for IE11 is Trident not MSIE . so I suppose that the reason why I got always notification to install java even its already installed .. but I cannot find temporarily solution for that as guys solve this issue by updating deployJava.js for webstart and by adding "trident" with "msie"...
just note that only windows 7 can install IE11 or its bundled with Windows 8.1 .. you cannot install IE11 or update it to IE11 on windows 8.
again and briefly my questions are :
1- where JavaFX app detect browser agent?
2- is it possible to the modify package that is responsible for that and include jar to project ?
any idea is welcomed ..
Internet Explorer 11 is not a supported configuration for JavaFX in JRE 7.
You can request support for Internet Explorer 11 by filing a feature request in the JavaFX issue tracker. You can link back to this question in your feature request.
I guess what you are saying in your question is that the information Microsoft place in the UserAgent string for IE11 has changed from previous versions and the way to understand the UserAgent string encoded information has changed in IE11 compared to earlier browser releases. These changes mean that the current JavaFX deployment code does not correctly detect it is running in an IE11 environment and perform appropriate operations to enable JavaFX applications to execute in IE11.
I believe that JavaFX packaging code uses a dtjava.js script to detect the target browser. For JavaFX 8 this detection routine is (I believe) the JavaScript detectEnv() method. What you might need to do to get IE11 compatibility is to host your own deployment scripts and replace the dtjava.js in your local deployment scripts with a modified version you have created which is IE 11 compatible (detailed instructions on how to do this are outside the scope of this answer). Even if you do get the dtjava.js script to correctly identify and execute logic for IE 11, there may still be other issues running JavaFX in IE 11 (due to it not being currently a supported deployment platform).
I've made some modifications in dtjava.js and got it to work in IE11
In my case I'm using dtjava.js only for embedding an applet not based in JavaFX, so probably these modifications are not enough to make a JavaFX application run.
I changed the IE detection rule from
ie = isDef(window.execScript);
to
ie = /trident/.test(u);
in detectEnv()
and
if (isDef(d.addEventListener)) {
d.addEventListener("DOMContentLoaded",
invokeCallbacks, false);
}
if (ua.ie && ua.win) {
with
if (isDef(d.addEventListener)) {
d.addEventListener("DOMContentLoaded",
invokeCallbacks, false);
}
else if (isDef(d.attachEvent)) {
in init() function.
Of course, these are hacky changes not very tested (only Explorer 10, 11 and latest FIrefox and Chrome). Follow at your own risk...
We have just moved an old website to a new hosting company who has ABCPDF version 7 installed on a Windows Server 2012 VPS.
Unfortunately the existing code is not working and from my research it is due to version 7 not being compatible with later versions of IE, such as that installed on Server 2012.
So I was trying to switch to use the Gecko engine. I installed Firefox on the server. And added the code to the Classic ASP script straight after the doc object was created:
doc.HtmlOptions.Engine = 1
Unfortunately this results in the following error:
Object doesn't support this property or method: 'HtmlOptions.Engine'
How can I change to use the Gecko engine, and am I doing this right or is there some other issue?
As a last resort is it possible to install an older version of IE on Server 2012?
I think you probably have no choice but to pay for a later version. I've been there myself
Gecko support was introduced in v8, and it looks as if it uses its own modified version of the display engine rather than the one which comes with Firefox. However as V8 and above support current versions of IE you probably wouldn't want to bother with Gecko.
http://www.websupergoo.com/abcpdf-13.htm
Re Internet Explorer 8 - which is the version I think you need for old versions of ABCpdf - if your server came with IE8 installed to begin with and it's been automatically updated, then it should in theory be possible to roll back to the previous version, or even rebuild the server from scratch, and then block windows update from updating IE. If it came with IE9 or above then you really do need to upgrade ABCpdf
i am using Netbeans PHP + Firefox 4 on Windows for my web development.
I've used a common firebug extension called Xrefresh. It was automaticlly refreshing my opened firefox tab everytime change in my projects directory occured, so pressing ctrl+s in netbeans was triggering auto-refresh in the browser. Very comfort way to work with css, almost live preview.
But now since new Firefox and Firebug versions Xrefresh doesn't work anymore and the question is - are therey any good alternatives, or does someone know how to configure Xrefresh now?
Without live preview my development is somehow slower.
https://github.com/NV/auto_update_stylesheets
This could help you. It refreshes the page via ajax on css save.
There's an automatic refresh-on-change tool for IE. It's called ReloadIt, and is available at http://reloadit.codeplex.com . Free.
Not an add-on to IE, but more of an "adjunct". It does not change the IE install, does not install a BHO or anything like that. So very low-impact installation.
You choose a URL that you'd like to auto-reload, and specify one or more directory paths to monitor for changes. Press F12 to start monitoring.
After you set it, minimize it. Then edit your content files. When you save, the page gets reloaded. like this:
I've managed to keep using xrefresh up until Firefox 9 however I'm not having any luck with version 10.
I've now switched to livereload, they've had a decent Mac version out for a while and a very experimental Windows version has recently been released.
Flex 3 debugging not working with FIREFOX 3 (under vista)
no trace() shown in console. breakpoints not working.
Do you have Flex Builder installed? If not, if you are using the free SDK, did you install the debug version of the Flash player?
Try reinstalling the debug version of the Flash player. Here's a link, in case you didn't. I had the same problem a week back -- corrupted my install. But also check out the config files as suggested in the other answer.
It worked perfect after installing the debugger from the link given above.
The exe that should be installed is listed as "Download the Windows Flash Player 10.1 ActiveX control content debugger (for IE) (EXE, 2.72 MB) " in http://www.adobe.com/support/flashplayer/downloads.html.
Do you have:
ErrorReportingEnable=1
TraceOutputFileEnable=1
In a file called mm.cfg in your home directory? I'm using FF3 on Windows Server 2k3 and it works fine, so I can't speak to why it wouldn't work on Vista. Despite Vista's reputation for being broken, I doubt that this is a Vista-only problem you're experiencing. You're sure you've got the debugging flash player installed?