- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 Oct 2013 16:09:11 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23481
Bug ID: 23481
Summary: [Shadow]: Multiple trees are introduced to explain
encapsulation.
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: johnjbarton@johnjbarton.com
QA Contact: public-webapps-bugzilla@w3.org
Blocks: 14978
" Encapsulation is effectively a natural property of having multiple trees."
I pondered the first part of this document for a long while: "tree of trees"
makes no sense. Graphically, a tree of trees is just a tree. Look at all the
diagrams in the first part of the doc: just trees with solid or dotted lines
and some superfluous-looking boxes.
Eventually it came to me: 'tree of trees' was invented to explain that parts of
the tree are encapsulated from other parts. Eventually this was confirmed in
the quote above.
The story would be much clearer if you say that right when you introduce the
neology 'tree of trees'. Rather than starting with complicated definitions,
just say that the Shadow DOM spec defines new encapsulated DOM sub-trees. When
we introduce this encapsulated sub-tree into the existing DOM tree, we call the
result a 'tree of trees' to emphasis the encapsulation while also showing that
tree navigation operation existed between pre-shadow-DOM nodes and Shadow DOM
nodes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 10 October 2013 16:09:13 UTC