Community
Participate
Working Groups
I have IE9 installed on my machine. If I run the following little HTML on the IE browser directly, I get the expected output that CSS opacity is supported. If I run the same in the embedded IE, it says that it doesn't support opacity, but it still says that it is running in IE9 mode. ============= <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.0/jquery.min.js"> </script> <script type="text/javascript"> if (jQuery.browser.msie) { alert("I am IE "+jQuery.browser.version); } if(jQuery.support.opacity) { alert("I support opacity"); } else { alert("I DO NOT support opacity"); } </script> </head> <body> </body> </html> ================ Repro is simple: Just create a HTML file in a project, paste the text above and choose "Open with"->"Web Browser". I have experimented with FEATURE_BROWSER_EMULATION registry key and the corresponding property "org.eclipse.swt.browser.IEVersion", e.g. with value "9999", but without luck. Thanks, Reiner.
The issue seems to be caused by fact that Eclipse.exe is compiled with old Visual Studio compiler(see Bug 371500). If Eclipse is stared e.g. with Javaw.exe, the problem does not occur. Perhaps Windows detects Eclipse.exe to be old and switches to a kind of "Compatibility" mode.
Hi Reiner, Your SWT application with embedded IE seems to get stuck to a particular IE Compatibility Version, but when run with different application name JAVAW.exe, it works fine. Your scenario looks similar to bug 440300 fixed recently in 4.5M1 and 4.4.1RC1 builds. This issue occurs only when Eclipse/Embedded IE application is forcefully terminated(or gets crashed), leading to issue w.r.t. Windows registry entry for 'Application name' verses 'IEVersion' value. Suggest you to try out any of the latest Milestone builds: http://download.eclipse.org/eclipse/downloads/drops4/S-4.5M1-201408062000/#SWT or http://download.eclipse.org/eclipse/downloads/drops4/M-4.4.1RC1-201408130800/#SWT
I came across this issue in Eclipse Neon RC2. When starting an application from within the IDE the opaque items are rendered correctly. Exporting the application and starting it with eclipse.exe the opaque icons are not rendered at all. Starting the application via java -jar plugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar the opaque items are rendered correctly. I'm not sure what is causing this or if there is still an issue with the Windows registry items. I tested this on Windows 7 and Windows 10 and see the same issues. I will attach a sample to show the issue.
Created attachment 262000 [details] nattable richtext example to show the issue Attached feature based product projects to show the issue. When starting the application from the IDE you can edit items in the last column which opens the ckeditor based RichTextEditor in an SWT Browser. The editor will show all icons in the toolbar. After exporting and launching the application via Equinox launcher, not all icons will be visible (the disabled icons that use opacity doesn't appear). Starting the app via java or javaw will show all icons in the toolbar. So for me it seems to be somehow related on how the app is started via Equinox launcher. Not sure if the bug that was linked here is related. Note that you need the NatTable Core and the NatTable Nebula Extension feature installed (the later contain the necessary Nebula RichText dependency aswell)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
