- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Dec 2014 01:35:03 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27222 --- Comment #8 from Koji Ishii <kojiishi@gmail.com> --- Here's my first proposal for all attributes currently in the HTML spec: 1. Following attributes use the composed tree when the spec defines to traverse ancestors/descendants: - accesskey - draggable - dropzone - lang/xml:lang - title[*1] - ARIA (role, aria-*)[*2] 2. Following attributes use the DOM standard and do NOT propagate among trees: - contenteditable[*2] - dir[*3] - spellcheck - translate 3. Following attributes do not rely on ancestors/descendants and therefore out of scope from this discussion (included here for review and discussion purpose only): - class - contextmenu[*4] - data-* - hidden - id - itemid - itemprop - itemref - itemscope - itemtype - style - tabindex - name - dirname - maxlength - minlength - disabled[*4] - autofocus[*4] - inputmode[*4] - autocomplete [*1] Boris pointed out that implementations use event bubble, so using composed tree could make the spec different from implementations. We could use event path here, but I think the difference is subtle enough for implementations not to be required to change the existing code. [*2] These are already defined in the spec. [*3] Though dir attributes do not propagate, I think we need to force shadow hosts to compute the "unicode-bidi" property to "isolate". Still confirming with bi-di experts at: http://lists.w3.org/Archives/Public/www-style/2014Dec/0282.html [*4] These are UI related, and they affects descendants in normal DOM tree. Should we propagate these to shadow trees? Reviews/thoughts/opinions are greatly appreciated. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 18 December 2014 01:35:05 UTC