Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make things focusable in CSS #3374

Closed
frivoal opened this issue Dec 3, 2018 · 2 comments
Closed

Make things focusable in CSS #3374

frivoal opened this issue Dec 3, 2018 · 2 comments

Comments

@frivoal
Copy link
Collaborator

frivoal commented Dec 3, 2018


Migrated from WICG/spatial-navigation#25
Originally created by @frivoal on Fri, 16 Feb 2018 06:41:17 GMT


Other specs (most likely HTML) will probably find it convenient if we define a hook in the "Handling key presses" section to let them define what a particular element does when arrow keys are pressed and that element wants to respond (e.g. the <select> element changing which is the currently selected <option>).

EDIT: The discussion in this issue moved to a completely different, and more interesting topic. Repurposing the issue to talk about that.

@bkardell
Copy link
Contributor

bkardell commented Dec 3, 2018

I know I have raised this point a really lot of times, including in csswg originally and in pretty much every meeting we've had but it is somehow it is not captured in the linked issue, so let me try to leave some kind of indicator here so that it doesn't get lost.

Focus management itself is incredibly wonky and magical already. There are few things in the platform so central and critical and yet exposed in such a way that it's going to take some real thought to dig out of. I've mentioned a number of these issues in discussion and don't want to bog the post down with them here but, I would be very, very wary of adding significant new complexity like this to the problem space until we've deal with some of that.

@frivoal
Copy link
Collaborator Author

frivoal commented Dec 4, 2018

Oops. The issue migration script created some duplicates. #3379 is the same as this one, but with all the other comments from the original issue, while this one only has the opening one. I'll close this one, and move @bkardell 's comment

@frivoal frivoal closed this as completed Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants