[Bug 23887] [Shadow] Put only the final destination insertion point to the event path

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

--- Comment #18 from Hayato Ito <hayato@chromium.org> ---
(In reply to Steve Orvell from comment #16)
> (In reply to Hayato Ito from comment #9)
> > This might be a good opportunity to discuss how event path should be.
> > 
> > In the most *strictest* world, I don't think we should add either insertion
> > points, whether it's final destination or not
> 
> I would prefer this to the proposal here (only the last insertion point in
> the path).
> 
> If insertion points are sometimes in the path, I worry that it will be too
> confusing to know when they can be used and it will become an anti-pattern
> to attach listeners there.
> 
> So my preferences in order are:
> 
> 1. all insertion points in event path.
> 2. no insertion points in event path.
> 3. last insertion point in event path.

Thank you. That means 2 is an acceptable proposal?

I wonder whether there is a missing piece of APIs or not in order to accept 2.

For example,

> Need to perhaps change getDistributedNodes() handling a bit to make it
> useful, since one should be able to observe changes to that list.

Adding an such event, like distributionChanged, would be useful to accept 2?

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

Received on Thursday, 28 November 2013 02:04:37 UTC