Closed
Bug 1421568
Opened 7 years ago
Closed 7 years ago
Add a ChromeOnly method to access also closed shadow roots
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(1 file)
3.46 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
I'm pretty sure we'll want to have this for devtools and such.
Updated•7 years ago
|
Priority: -- → P2
Addons will need something like this too, otherwise websites would be able to hide pretty much all their content from addons. Addons would be forced to do some xray dances on document_start to intercept every |attachShadow| call and then implement custom shadow tree traversal over the intercepted roots if they wanted to handle with that.
If mozilla plans to use shadow dom for internal components too and those are not intended to by accessed by extensions then there might be a need for a 3-tier distinction:
- open
- closed (accessible by extensions)
- closed-chrome (only accessible by system principal)
Or maybe this can be covered by giving internal shadow trees different node principals than content-created shadow trees.
Assignee | ||
Comment 2•7 years ago
|
||
We may want to do something more complicated for extensions, but for now, just this simple thing.
Assignee: nobody → bugs
Attachment #8945126 -
Flags: review?(mrbkap)
Updated•7 years ago
|
Attachment #8945126 -
Flags: review?(mrbkap) → review+
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/42d3af626b31
Add a ChromeOnly method to access also closed shadow roots, r=mrbkap
Comment 4•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•