Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 421905 - When Browser is using XULRunner, the evaluate browser function always returns null
Summary: When Browser is using XULRunner, the evaluate browser function always returns...
Status: CLOSED DUPLICATE of bug 465757
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.3   Edit
Hardware: All Windows All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-17 06:57 EST by Nat G CLA
Modified: 2015-04-29 08:04 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nat G CLA 2013-11-17 06:57:12 EST
I'm referring to the SWT.MOZILLA browser style.  I am using 32 bit java because XULRunner for windows only has a 32 bit version.  Using alternative browsers in SWT seems like a dark jungle full of pitfalls.

I have been checking through all the different available versions of XULRunner to see which one works best.  I found that XULRunner 17.0 is the one that works the best.  It doesn't produce any errors and it loads properly, but the problem happens when I try to use the "evaluate" command.  Evaluating javascript code always returns "null" with "evaluate", whereas, when I use the "execute" method, the javascript executes successfully.

Is there any version of XULRunner where the evaluate command returns results properly with the SWT browser?  I know that newer versions of XULRunner don't use Java XPCOM so I was wondering if there's ever going to be a proper fix for this in SWT, either to use newer versions of XULRunner or to make XULRunner with Java XPCOM work properly.

Also, Is there any version of XULRunner prior to 17.0 where "evaluate" and "execute" both work properly besides 1.9.2, etc.?  1.9.0 and 1.9.2 seem too old to handle HTML5 gracefully.
Comment 1 Grant Gayed CLA 2013-11-25 10:37:29 EST
Browser support for XULRunner 17 was never declared, though on Windows and OSX it does mostly work in Eclipse 4.3.x (with the exception of evaluating JS).  For now you need to use XULRunner 10, and note that XULRunner 17 will no longer work at all as of the Eclipse 4.4 release.

Eclipse 4.4 will have support for XULRunner 24, assuming that the legal clearance for it is received from the Eclipse Foundation (the implementation work is already complete).

Closing report since XULRunner 17 is a supported release.
Comment 2 Grant Gayed CLA 2013-11-25 10:38:53 EST
(In reply to Grant Gayed from comment #1)

I meant to say: Closing report since XULRunner 17 is NOT a supported release.
Comment 3 Arun Thondapu CLA 2015-04-29 08:04:26 EDT
Apparently this bug happens in other XULRunner versions as well, as mentioned in bug 465757, marking as duplicate.

*** This bug has been marked as a duplicate of bug 465757 ***