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

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

--- Comment #20 from Hayato Ito <hayato@chromium.org> ---
If there is no objection to remove insertionoParent in a few days, let me
remove the experimental support from blink. I am assuming no one is currently
using that.

I'd like to provide an alternative which meets a requirement.
That should be renderParent (or composedParent?), which skips insertion points.

I am not sure whether renderParent is good name or not. Any suggestions?


(In reply to comment #19)
> Thank you the comments. Let me summarise the discussion so far:
> 
> - We need event.path() to address the use case described in
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21066
> 
> - We don't need insertionParent, which doesn't meet any requirement of any
> use cases. We can remove insertionParent.
> 
> - We still need another API to address the use case, 'Traversing up the
> composed tree'. The API's name might be either 'renderParent' or
> 'composedParent'. We might need a list of insertionPoints which are skipped.

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

Received on Wednesday, 22 May 2013 05:46:17 UTC