Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 398070 - BrowserFunction not converting correctly boolean arrays with XULRunner 10
Summary: BrowserFunction not converting correctly boolean arrays with XULRunner 10
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.8.1   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: 4.3 M5   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 407960 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-14 07:03 EST by Peter Severin CLA
Modified: 2013-05-16 15:58 EDT (History)
1 user (show)

See Also:

Attachments
A snippet that shows the issue with boolean arrays (1.85 KB, text/x-java)
2013-01-14 07:03 EST, Peter Severin CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Severin CLA 2013-01-14 07:03:49 EST 
Created attachment 225562 [details]
A snippet that shows the issue with boolean arrays

It looks like there is an issue with converting boolean array parameters that are passed to BrowserFunction. I attached a snippet that shows the issue. When passing an array like [false, false, false, false, false], instead of an array with false values the function receives an array with random boolean values.

I'm doing my tests with XULRunner 10 but I believe that the bug can be reproduced with previous versions too.
Comment 2 Peter Severin CLA 2013-01-25 08:54:54 EST 
Thanks for the quick fix! Will it be also available in 3.8.2?
Comment 3 Grant Gayed CLA 2013-01-25 09:12:17 EST 
No, it's late in the cycle for submissions to 3.8.x/4.2.x, and I'm not sure that the severity of the issue would have warranted it regardless.  Possible workarounds in the meantime are to either use a native renderer != XULRunner 10 (eg.- XULRunner 3.6.x works fine), or to pass numbers instead and to interpret them on both ends as representing boolean values.
Comment 4 Grant Gayed CLA 2013-05-16 15:58:10 EDT 
*** Bug 407960 has been marked as a duplicate of this bug. ***