[Bug 24421] [Shadow]: Clarify that Shadow DOM spec takes care of nodes which are *inDocument*.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24421

--- Comment #9 from Erik Arvidsson <arv@chromium.org> ---
(In reply to Olli Pettay from comment #8)
> (In reply to Hayato Ito from comment #4)
> > In the current implementation of blink (and WebKit), if an event happens on
> > a disconnected node, it's event path will contain only one node, the node
> > itself. Bubbling doesn't happen at all.
> > See
> > https://code.google.com/p/chromium/codesearch#chromium/src/third_party/
> > WebKit/Source/core/events/EventPath.cpp&q=EventPath&sq=package:chromium&l=149
> Is that even for nodes not in shadow DOM? Sounds like a major bug.
> Whether or not node is in document must not affect at all to the
> event propagation.

It is a major WebKit/Blink bug and once it is fixed it would be confusing if
the event path is different whether disconnected or not.

To me it is obvious that things should work the same whether in document or
not. Composition is not related to in document in any way and adding that
restriction is a very arbitrary exception. One might as well say that "display:
none" elements have no distribution, or that we do not distribute on the leap
day.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 10 February 2014 15:03:20 UTC