Community
Participate
Working Groups
A change (bug?) has been introduced in the JavascriptCore component that accompanies WebKitGTK. As of WebKitGTK 1.4 the JSValueToBoolean() API now fails to resolve a boolean JSValueRef to 0 or 1, and as a result the Browser is interpreting all passed booleans as true since their values != 0. This is a regression relative to WebKitGTK 1.2, where passed boolean values are being resolved fine.
Fixed in the 3.8 stream, patch is at http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=c9bd1fa15de6e698115cdc36e7f63af25f01eda4 . This should go into the 3.7.2 stream as well. It affects users of BrowserFunction, which includes the Browser itself (eg.- its close() API). BG added for a review.
Same fix released to 3.7.2 stream > 20120110, closing report.