- From: <bugzilla@jessica.w3.org>
- Date: Fri, 14 Nov 2014 08:18:10 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26365 --- Comment #47 from Hayato Ito <hayato@chromium.org> --- Here is the filed chrome bugs: - iframe: https://code.google.com/p/chromium/issues/detail?id=393350 - script: https://code.google.com/p/chromium/issues/detail?id=394327 - accesskey: https://code.google.com/p/chromium/issues/detail?id=394295 - label: https://code.google.com/p/chromium/issues/detail?id=394307 - doucment.currentscript: https://code.google.com/p/chromium/issues/detail?id=394332 - attachedCallback (custom elements): https://code.google.com/p/chromium/issues/detail?id=426050 I think the intentional exception in the current blink's implementation is <base> and <link> elements. See 7.1 Inert HTML Elements: http://w3c.github.io/webcomponents/spec/shadow/#inert-html-elements I think the paragraph in the Shadow DOM spec: > 7.1 Inert HTML Elements > All other HTML elements in the shadow trees must behave as if they were part of the document tree. must be updated. Further more, we can remove this 7.1 section from the Shadow DOM spec if we finish all tasks here, hopefully. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 14 November 2014 08:18:12 UTC