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

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

--- Comment #18 from Steve Orvell <sorvell@chromium.org> ---
So, we can remove event path from the list of reasons we need an api to 'for a
given node, find its ancestors in the composed tree'.

However, as Elliot points out, there are other reasons we need this information
(see above). He also separately mentioned the need to discover if a node
visible in an overflow scrolling block.

One option is that we could address each of these use cases independently and
add api to address them, as we've done with event.path(). That seems
impractical and that leaves us with needing the general api.

As previously mentioned, reprojection makes insertionParent insufficient for
constructing the list we want; however, we probably do not need actual
insertion points in the list of ancestors. Instead we can live with 'ancestors
in the composed *render* tree'.

Given this, we can replace insertionParent with renderParent or composedParent
and this would point to the parent of the last insertion point to which a node
is distributed. This should be enough to generate the necessary list.

If we decide we do need insertion points in the list of ancestors, we could
change insertionParent to insertionPath and this would be a list of insertion
points to which the node is distributed.

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

Received on Saturday, 18 May 2013 01:27:45 UTC