Re: [whatwg/dom] Node.prototype.rootNode is not Web compatible (#241)

FWIW, I don't like 'piercing', especially when going from shadow->light DOM way.
Shadow is supposed to be able to access light DOM, so there isn't really 'piercing' happening.
Piercing selector was other way round.

> The current contenders are treeTop and highestNode. I think we should pick one or the other.
> 
> nodeTreeRoot and treeTopNode would work but it's a bit long.

Note, the length of highestNode is the same as length of treeTopNode.

To my non-native-English-speaker ears 'highest' gives a bit wrong associations. Sounds like somehow qualifying thing.
treeTop or nodeTreeRoot or nodeTreeTop feel better.

But I start to like findRootNode(). It deals with the current node tree, and then once we figure out what kind of parameters would be good for it,  it could deal with also ancestor node trees.
And not having it as a property, at least to me, hints that the operation isn't necessarily O(1).
(I assume it will be O(1) within same node tree, but not necessarily when dealing with multiple nested shadow trees)

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/241#issuecomment-217088982