Open
Bug 1436254
Opened 6 years ago
Updated 2 years ago
consider exposing XPathResult through importGlobalProperties
Categories
(Core :: DOM: Core & HTML, enhancement, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: heycam, Unassigned)
Details
In bug 1435666, we remove nsIDOMXPathResult and hard code some constant values we used from it. Maybe we should add XPathResult to the list of interfaces supported by importGlobalProperties, and get the values from there.
|
||
Comment 1•6 years ago
|
||
Why don't you use [exposed=Symtem]?
|
Reporter | |
Comment 2•6 years ago
|
||
That's another option, though I'm not really sure how we decide whether we want to unconditionally expose particular interfaces to system globals or instead make them opt-in with importGlobalProperties.
|
|
||
Comment 3•6 years ago
|
||
IIRC we added `importGlobalProperties` because unconditionally-added `URL` broke the world. But it is no longer a problem. (Legacy add-ons are dead, const is no longer defined on the global.) IMO we should drop `importGlobalProperties` now.
|
||
Comment 4•6 years ago
|
||
Hey, can you set a priority for this so it'll disappear from triage? Thanks!
Flags: needinfo?(cam)
|
|
Reporter | |
Updated•6 years ago
|
Flags: needinfo?(cam)
Priority: -- → P5
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•