Closed
Bug 803606
Opened 13 years ago
Closed 13 years ago
Consider reversing the order of JSSLOT_PROXY_HANDLER and JSSLOT_PROXY_PRIVATE
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla20
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
1.27 KB,
patch
|
Waldo
:
review+
|
Details | Diff | Splinter Review |
The win here would be that slot 0 would be up for grabs on both proxies and non-proxies, so someone who needs to have a mix of the two with a single slot of important info could use slot 0 for both. This would let us get rid of some complexity in DOM binding code, and should make it easier to do jitcode that has to work on both DOM proxies and regular DOM objects.
![]() |
Assignee | |
Comment 1•13 years ago
|
||
Attachment #687795 -
Flags: review?(jwalden+bmo)
![]() |
Assignee | |
Updated•13 years ago
|
Whiteboard: [need review]
Updated•13 years ago
|
Attachment #687795 -
Flags: review?(jwalden+bmo) → review+
![]() |
Assignee | |
Comment 2•13 years ago
|
||
Assignee: general → bzbarsky
Flags: in-testsuite-
Whiteboard: [need review]
Target Milestone: --- → mozilla20
Comment 3•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•