Shadow DOM should not be leaked via window or document |
||||||
Issue descriptionAFAIK, the followings must be checked again before shipping v1. - document.currentScript - window.history - https://github.com/w3c/webcomponents/issues/184 - document.activeElement (This was done, however, the spec is being updated) - Spec issue: https://github.com/w3c/webcomponents/issues/358 - URL fragment - Spec issue: https://github.com/w3c/webcomponents/issues/66 - window named properties - https://github.com/w3c/webcomponents/issues/145 We have to make sure that Blink honors the spec, or update the spec if necessary.
,
Mar 30 2016
,
Mar 30 2016
,
Mar 30 2016
Please add any item to this bug if you find anything which must be checked.
,
Mar 31 2016
,
Mar 31 2016
- window.frames
,
Apr 1 2016
,
Apr 11 2016
,
Apr 25 2016
fullscreen: https://github.com/w3c/webcomponents/issues/180
,
Apr 25 2016
pointerlock: https://github.com/w3c/webcomponents/issues/192
,
Apr 25 2016
iframe issues: https://github.com/whatwg/html/issues/763
,
Apr 25 2016
document.activeElement/ShadowRoot.activeElement is done (https://github.com/w3c/webcomponents/issues/358).
,
Apr 25 2016
URL fragment (https://github.com/w3c/webcomponents/issues/66) is done. fragment will not be followed in shadow trees.
,
May 11 2016
window.frames is already solved by a part of issue 473518 , https://codereview.chromium.org/1132133009 and so on.
,
Jun 22 2016
Can we close this?
,
Jun 23 2016
Let's close this. Remaining items are tracked at: Link target: issue 610952 pointerLock: issue 622584 fullscreenElement: issue 622585 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by hayato@chromium.org
, Mar 30 2016