329058 – BrowserFunction should map java null to JS null, not to undefined

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 329058 - BrowserFunction should map java null to JS null, not to undefined

Summary: BrowserFunction should map java null to JS null, not to undefined

Status:	RESOLVED FIXED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	SWT (show other bugs)
Version:	3.7
Hardware:	PC All

Importance:	P3 normal (vote)
Target Milestone:	3.7 M4
Assignee:	Grant Gayed
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-10-29 11:45 EDT by Grant Gayed
Modified:	2010-11-15 16:08 EST (History)
CC List:	2 users (show)

See Also:

Attachments
patch (7.01 KB, patch) 2010-11-15 16:05 EST, Grant Gayed	no flags	Details \| Diff
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 Grant Gayed

2010-10-29 11:45:48 EDT

Comment 1 B. Chen

2010-11-02 14:24:02 EDT

Any chance this will be fixed in SWT 3.6.2?

Comment 2 Grant Gayed

2010-11-02 14:41:23 EDT

No, it's not critical to eclipse, and would require new API in some form.

Comment 3 Grant Gayed

2010-11-15 16:04:13 EST

Discussed with SSQ, differentiating between JS null and JS undefined on the Java side is not appropriate.  Changing report title to the remaining outstanding issue, which is that Java null should be mapped to JS's null value, not to undefined.

Comment 4 Grant Gayed

2010-11-15 16:05:45 EST

Created attachment 183169 [details]
patch

Comment 5 Grant Gayed

2010-11-15 16:08:37 EST

fixed > 20101115