Community
Participate
Working Groups
Support for Xulrunner 24 is planned for eclipse 4.4. The implementation work is complete and is waiting for the legal clearance from the Eclipse Foundation.
Legal approval has been received for this. I will merge it into master after the current milestone has passed.
The changes are merged into master > 20140102. The commits are as follows (99% of the changes are in the first commit): - http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=423e6311c6f620961a89db2328255074c119d207 - http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=5c344373bd6752d7933887eed3d787555f18fafc - http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=f8f9e0f937700f96144187bcc1bc9dd15e054856 - http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=70c8157b90cf2b2943e20b95e4895662735218d5 - http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=b39bcb22f405f03e90733595e8886bcfd30563c4 Leaving report open since it is a 4.4 plan item.
Additional commits related to this: - http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=481ef89ba9e4810894860e8d68c4f8217fc3cec1 - http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=f6af9061bfda95d3bf04fcaacdf30d36835f5f6f - http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=8676bb36dcbafd1a692b72f2627310790f5b9efb
Windows x86_64 support: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=4c5598839063d275b966ef445aff2c758bb7f245
The comment 4 commit is not complete, this ensures that the library builds on hudson: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=14d3ce4da57b33221606a768f517941e568c2e57 .
Marking the bug as Fixed in M5.
*** Bug 327696 has been marked as a duplicate of this bug. ***
Thanks for the work! Does the new integration also support WebGL?
*** Bug 428930 has been marked as a duplicate of this bug. ***
(In reply to Erdal Karaca from comment #8) > Thanks for the work! Does the new integration also support WebGL? I've looked into this, and the apparent non-support seems to be due to a difference between the xulrunner 24 and firefox 24 binaries from mozilla.org. In particular, the common layout/build/nsLayoutModule.cpp:1140-1143 has: { "@mozilla.org/content/canvas-rendering-context;1?id=experimental-webgl", &kNS_CANVASRENDERINGCONTEXTWEBGL_CID }, #ifdef MOZ_PHOENIX // Not MOZ_FENNEC or MOZ_B2G yet. { "@mozilla.org/content/canvas-rendering-context;1?id=webgl", &kNS_CANVASRENDERINGCONTEXTWEBGL_CID }, #endif The purpose of the "#ifdef MOZ_PHOENIX" is to ensure that full WebGL compliance is not claimed for their builds that target mobile, where there are presumably technical limitations to achieving this. Unfortunately this #ifdef is precluding XULRunner since it also does not define MOZ_PHOENIX. That being said, I think the only difference between canvas.getContext("webgl") and canvas.getContext("experimental-webgl") is that the latter comes with a caveat that the full set of compliance tests was not passed by the renderer. It does not reduce its abilities per se, and I believe that XULRunner 24's WebGL rendering abilities are actually identical to those in Firefox 24, they just are only accessible through canvas.getContext("experimental-webgl"). https://bugzilla.mozilla.org/show_bug.cgi?id=870232 indicates that the abilities here vary by platform, not by product. FWIW I notice that in their trunk this line has changed to "#ifdef MOZ_WEBGL_CONFORMANT", so depending on which builds they set this for, it's quite possible that newer XULRunner releases do now give an answer for canvas.getContext("webgl").
It seems that the security context that the javascript executes under has now changed, as I used to be able to execute code like: window.QueryInterface(Components.interfaces.nsIInterfaceRequestor).getInterface(Components.interfaces.nsIDOMWindowUtils).getOuterWindowWithId(99).QueryInterface(Components.interfaces.nsIInterfaceRequestor).getInterface(Components.interfaces.nsIWebNavigation).QueryInterface(Components.interfaces.nsIDocShell).allowJavascript=false; I'm not sure that this change (presuming it is intentional) is documented anywhere currently? Is there a recommended migration for running chrome code from SWT?
(In reply to Matt Mising name from comment #12) This difference is not intentional, something has changed in XULRunner between their 10 and 24 releases. I've logged bug 431839 for this.
