| Summary: | BrowserFunction should map java null to JS null, not to undefined | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Grant Gayed <grant_gayed> | ||||
| Component: | SWT | Assignee: | Grant Gayed <grant_gayed> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cbeth, mukund | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | 3.7 M4 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Grant Gayed
Any chance this will be fixed in SWT 3.6.2? No, it's not critical to eclipse, and would require new API in some form. 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. Created attachment 183169 [details]
patch
fixed > 20101115 |