- From: <bugzilla@jessica.w3.org>
- Date: Wed, 07 Jan 2015 02:14:27 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27222 --- Comment #19 from Koji Ishii <kojiishi@gmail.com> --- Further revised proposal here. First, define 3 ways to traverse trees. There are 3 ways to traverse trees: 1. Traverse within each tree of trees. When processing attributes that belong to this category requires traversing the DOM tree, it must traverse only within each DOM tree. This is the default behavior. Unless specifically specified, all attributes belong to this category. If UA uses CSS properties to implement the attribute, it must prevent inheriting the property at the DOM tree boundaries so that the behavior is consistent with UA that does not use CSS properties to implement the attribute. 2. Traverse using composed tree. 3. Traverse within each tree of trees, then recursively at Shadow Root or Shadow Host. When traversing ancestors of a Shadow Root, UA must traverse the Shadow Host it belongs to and its ancestors. Similarly, when traversing descendants of a Shadow Host, UA must traverse its shadow roots and their descendants in the youngest to the oldest order, before traversing the descendants of the Shadow Host. With these definitions, my proposal is as below. Attributes that belong to the traversal type 2: - draggable - dropzone - hidden - title Attributes that belong to the traversal type 3: - accesskey - lang/xml:lang - spellcheck Following attributes are being discussed at bug 25473: - autofocus - tabindex All other attributes that are not listed here belong to the traversal type 1, as defined above. Thoughts/opinions are appreciated. Happy new year. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 7 January 2015 02:14:29 UTC