[Bug 21066] Provide an event path API

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

--- Comment #24 from Scott Miles <sjmiles@chromium.org> ---
Components need to be able to work with elements that are supplied to them from
the outside and projected into shadow-dom (aka distributed elements). Those
elements have different positions in the tree depending on your point of
reference. 

In general, components (internally) need event.path in order to process events
that have bubbled up from distributed elements. I don't believe there is any
encapsulation problem here.

The alternative is attaching listeners explicitly to all possible useful
targets, which can be extremely inefficient (see first note in this thread).

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

Received on Wednesday, 24 April 2013 22:29:21 UTC