The changes in org.eclipse.atf.mozilla.swt.browser don't address https://bugs.eclipse.org/bugs/show_bug.cgi?id=201774.
Until the XULRunner extension issue is handled by the platform, we'll need for the org.eclipse.atf.mozilla.swt.browser plugin to load at startup in order to set the XULRUNNER_PATH property. Currently (even with these latest changes), the XULRUNNER_PATH property is only set when opening the ATF MozBrowserEditor. However, if the SWT Browser is instantiated before MozBrowserEditor, then XULRUNNER_PATH is never properly set, and ATF will not function as expected. So we would need to do the following changes: 1) Have org.eclipse.atf.mozilla.swt.browser plugin load & execute on startup, using the "org.eclipse.ui.startup" extension point. It would execute MozillaHelper.definedContributedXulRunner(). 2) Remove the line "MozillaHelper.definedContributedXulRunner(null)" from MozBrowserEditor.java. Javier Pedemonte ATF Developer
_______________________________________________ atf-dev mailing list atf-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/atf-dev
