Closed
Bug 589015
Opened 14 years ago
Closed 14 years ago
js_watch_set doesn't need that crazy dummy frame
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: luke, Assigned: luke)
Details
(Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file)
6.53 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
When there is both a watchpoint and setter on the same property, the result of the watchpoint is passed to the setter. As Blake explained: back in the day, before the age of wrapperization, there was a potential security hole whereby, e.g., content watchpoints could inject content values into chrome setters. That was the problem fixed by the dummy frame. With wrappers, though, there should be no such mingling and thus this dummy frame is no longer necessary. It's also a massive breaker of invariants I'd like to have for bug 539144.
Attachment #467615 -
Flags: review?(mrbkap)
Comment 1•14 years ago
|
||
Comment on attachment 467615 [details] [diff] [review] rm Woo-hoo!
Attachment #467615 -
Flags: review?(mrbkap) → review+
Comment 2•14 years ago
|
||
I managed to dis-remember this dis-gusting history. Kill this code with fire, salt the earth, drive it before you and hear the lamentation da wimmin! /be
Assignee | ||
Comment 3•14 years ago
|
||
Indeed, that is best in life. http://hg.mozilla.org/tracemonkey/rev/b22e82ce2364
Whiteboard: fixed-in-tracemonkey
Comment 4•14 years ago
|
||
http://www.youtube.com/watch?v=OBGOQ7SsJrw /be
Comment 5•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/b22e82ce2364
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•