You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
The text was updated successfully, but these errors were encountered: