Extensions' content scripts can't pierce closed shadow DOMs
Reported by
93m...@gmail.com,
May 7 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: 1. Enable experimental web features (to enable shadow DOM v1). 2. Visit https://fiddle.jshell.net/Lfa0c767/show/ 3. Try to access the shadow DOM containing the text "This is some test text" from an extension context. What is the expected behavior? A chrome extension can access the shadowRoot of an element with a closed shadow DOM. For example, on the linked page, I would expect an extension to be able to change the text "This is some test text". What went wrong? Chrome extensions can't access the shadowRoot of an element with a closed shadow DOM. Did this work before? No Chrome version: 52.0.2723.2 Channel: dev OS Version: Flash Version: Shockwave Flash 22.0 r0
,
May 11 2016
,
May 11 2016
This is working as expected, but maybe there can be an extension API to get closed shadow root, as this is also a popular demand from test automation / web debuggers (e.g. https://github.com/w3c/webcomponents/issues/354).
,
May 11 2016
Closing. Working as expected. You might want to file a feature request if you want to have an API for chrome extension. |
|||
►
Sign in to add a comment |
|||
Comment 1 by caseq@chromium.org
, May 9 2016