- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Jun 2017 08:40:23 +0000
- To: public-css-archive@w3.org
The discussion about HTML with the whatwg mentioned in the minutes above stalled here: https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Jan/0018.html Since then Edge, no longer supports bidirectional propagation of `:hover` and `:active`. Also, `:focus` does not propagate from the label to the labelled control (nor the other way around). I still think bidirectional propagation of `:hover` and `:active` would be nice, but it looks like the consensus is going away from it, and that everybody agrees `:active` and `:focus` are supposed to propagate differently. So the current phrasing in the spec seems wrong, and should be overturned. I propose to replace this: > If the document language has defined additional ways by which an element can match :active, the same ways must apply to elements matching :focus as well, except that the parent of an element that matches :focus must not match :focus. with that: > Document languages may define additional ways in which an element can match :focus, except that the parent of an element that matches :focus must not match :focus. (see :focus-within if matching on the parent is desired). While we're at it, this part of the definition also seems wrong: > There may be document language or implementation specific limits on which elements can acquire :focus. For example, [HTML5] defines a list of activatable elements. and should be replaced with > There may be document language or implementation specific limits on which elements can acquire :focus. For example, [HTML5] defines a list of focusable areas (https://html.spec.whatwg.org/multipage/interaction.html#focusable-area). -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1240#issuecomment-306420683 using your GitHub account
Received on Tuesday, 6 June 2017 08:40:30 UTC