[Bug 21066] [Shadow]: Provide an event path api

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

--- Comment #18 from Hayato Ito <hayato@chromium.org> ---
(In reply to comment #17)
> One idea is to make insertionParent() take additional parameter.
> 
> For example:
>    contentA.insertionParent(#one) -> contentB
>    contentA.insertionParent(#two) -> contentB2
> 
> Now, event.path can be emulated:
> 
>   var originalEventTarget = ....; // #one or #two
>   var element = originalEventTarget;
>   var eventPath = [element];
>   while (element.insertionParent(originalEventTarget)) {
>      element = element.insertionParent(originalEventTarget);
>      // element might be an 'insertion point' in this case.
>      eventPath.push(element);
>   }
> 
> WDYT? Is this a reasonable API?

My initial feeling is that this is not good API since it is likely to be
misused.
Just providing event.path API is much better.

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

Received on Wednesday, 24 April 2013 09:26:43 UTC