No named access on window for iframes in shadow DOMs
Reported by
93m...@gmail.com,
Mar 3 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce the problem: https://jsfiddle.net/3hacxgcp/ What is the expected behavior? The iframes have their browsing context names set to "testFrame1" and "testFrame2", and their WindowProxy objects accessible via window.testFrame1 and window.testFrame2 in the parent window. This behaviour would match the working draft https://html.spec.whatwg.org/multipage/browsers.html#named-access-on-the-window-object. In the JSFiddle, the text should read " Value from <iframe> in top-level DOM: value1 Value from <iframe> in shadow DOM: value2 " What went wrong? The second iframe, in a shadow DOM, isn't accessible from the parent window via window.testFrame2 (nor is it counted towards window.frames.length). The text in the JSFiddle reads " Value from <iframe> in top-level DOM: value1 Value from <iframe> in shadow DOM: undefined " Did this work before? N/A Chrome version: 48.0.2564.116 Channel: stable OS Version: Flash Version: Shockwave Flash 20.0 r0
,
Mar 4 2016
,
Mar 7 2016
,
Mar 30 2016
,
Mar 30 2016
,
Mar 30 2016
,
Apr 25 2016
,
Apr 25 2016
Corresponding discussion is going on at https://github.com/whatwg/html/issues/763 for standards.
,
May 11 2016
See issue 473518 for the implementation. The standard will be updated not to allow leaking names of iframes in shadow tree to document tree. On Chromium/Blink, the behavior won't change, and nothing can be done here. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dtapu...@chromium.org
, Mar 3 2016