- From: Brad Kemper via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Nov 2017 23:02:41 +0000
- To: public-css-archive@w3.org
I feel like this should be in a regular rule with a selector, instead of an at-rule, so that it can be scoped. I’m also concerned about how it may disable common arrow key interactions within native widgets or non-native components. Or conversely, how such focusable elements might prevent further navigation by trapping the arrow keys. Changing a SELECT menu or radio buttons typically requires use of the arrow keys. With radio buttons, for instance, right arrow and down arrow both work to go to the next radio button in the group, and the other arrows go to the previous radio button in the group. -- GitHub Notification of comment by bradkemper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1940#issuecomment-342990809 using your GitHub account
Received on Wednesday, 8 November 2017 23:02:53 UTC