- From: Brad Kemper via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Jun 2017 15:44:39 +0000
- To: public-css-archive@w3.org
I think it is great to have this pseudo-class, but the name of it is dumb (no offense). It is describing what it looks like, I guess (or maybe it will "ring" like a bell for assistive tech?), instead of describing an understandable state. It should be :keyboard-focus or :non-pointer-focus or something. WRT focus for attention/memory limitations, I think that is why type-able controls, like text fields, show focus regardless of input method. But clicking or tapping a button isn't something that requires you to know that it has focus (and in the standard Mac UI, it doesn't even move the focus out of a text field). So that should be part of the heuristics. That said, tabindex=0 does not really say much about whether focusing should be more like a text field or more like a button. I guess we could just continue to use :focus for text-fields. But it would be better if we had a css property (or @rule?) to make something focusable and to say what type of focus it should be. -- GitHub Notification of comment by bradkemper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/709#issuecomment-305534557 using your GitHub account
Received on Thursday, 1 June 2017 15:44:46 UTC