We previously discussed standardized keyboard behavior for select in these issues:
However, since then we have switched from creating a new element to using a CSS property to opt in to the new thing. In addition, @annevk gave feedback that the select element should respect platform conventions instead of having standardized keyboard behavior (correct me if I'm wrong).
During the call earlier today, @scottaohara expressed concern about changing keyboard behavior on a CSS property.
With this in mind, should we just not change the keyboard behavior for customizable select? Caveat that we are still going to not do selection-follows-focus anywhere in the new mode.
We previously discussed standardized keyboard behavior for select in these issues:
However, since then we have switched from creating a new element to using a CSS property to opt in to the new thing. In addition, @annevk gave feedback that the select element should respect platform conventions instead of having standardized keyboard behavior (correct me if I'm wrong).
During the call earlier today, @scottaohara expressed concern about changing keyboard behavior on a CSS property.
With this in mind, should we just not change the keyboard behavior for customizable select? Caveat that we are still going to not do selection-follows-focus anywhere in the new mode.