[Bug 21067] [Shadow]: Provide an api to insertionParent

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

--- Comment #21 from Steve Orvell <sorvell@chromium.org> ---
I prefer composedParent over renderParent; however, I am wondering about the
alternative of simply changing insertionParent to insertionPath. In this case,
insertionPath would be the list of insertion points to which a node was
distributed. Given this, I believe the full event.path could be constructed.
Hayato-san, I respect your knowledge of this topic, do you agree about this?

While the event path tree is not necessary for the use cases in this thread,
I'm not sure it's never necessary, and it seems odd to have event.path and
traversal via 'composedParent' produce a different tree. I'd rather err on the
side of providing more information.

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

Received on Wednesday, 22 May 2013 17:18:18 UTC