Open
Bug 793238
Opened 12 years ago
Updated 2 years ago
Allow chrome JS to create DOMError objects
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: fabrice, Unassigned)
References
Details
We are removing temporarily the 'builtinclass' from nsIDOMDOMError in bug 790870, but we need to have a proper way to let chrome JS get these objects from the c++ implementation.
Comment 1•12 years ago
|
||
If you remove builtinclass, make sure to go through all DOMError usage in C++ and check
if there are any static_casts to the actual implementation, since after removing builtinclass, those
casts may become security bugs.
Comment 2•12 years ago
|
||
s/may/will/
Reporter | ||
Comment 3•12 years ago
|
||
Thanks for the heads up. I checked current c++ usage and could not find any static cast.
Comment 4•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•