- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Oct 2014 10:49:28 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26365 --- Comment #23 from Hayato Ito <hayato@chromium.org> --- Good point. Unless otherwise noted, I think parent/child relations for nodes should mean the relation in a document tree or a shadow tree. The meaning shouldn't change. In regard to 'parent/child relation in composed trees', I've being using 'a parent node in a composed tree', for example, *unofficially*, in code reviews in chrome. We might want to have a better term. In regard to 'parent/child relation in a tree of trees', the situation is not so simple. Although I used a term of 'In a tree of trees (root is a document)' in the previous comment, this is a kind of abbreviation for 'In a node tree which participates in a tree of trees whose root tree is a document tree'. The participant of 'tree of trees' is not a node. That's a node tree. You might want to know that the spec already have terms, 'child or hosted shadow root' [1] and 'deep descendant' [2]. I've introduced that when I tried to introduce 'deepContains' [3]. I am aware that this definition doesn't define the tree order between sibling nodes in a *tree of trees* yet. [1]: http://w3c.github.io/webcomponents/spec/shadow/#dfn-child-or-hosted-shadow-root [2]: http://w3c.github.io/webcomponents/spec/shadow/#dfn-deep-descendant [3]: That's reverted in https://github.com/w3c/webcomponents/commit/463916e5873e99e43136ef4fe7e75b4da4c722aa -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 2 October 2014 10:49:29 UTC