[select] what should happen on key invocations when open state is true/false

[gregwhitworth]

Seems like two separate questions here:

1. On Mac, do browsers receive the same KeyDown event from fn+arrow that they would get from a "real" Home/End key? When I still had the macbook I tested here and found that this appears to be true, at least as far as key events are concerned. If the browser gets the same thing for fn+arrow as it does for "real" Home/End keys, then OpenUI shouldn't need to care about any distinction here; it can just refer to Home/End everywhere.
2. What is the right behavior for key events received by the button part when the <select> is closed, given that there are differences between browsers and OS's?

For (1), unless we have evidence that fn+arrow sends something other than Home/End to the browser, I think we should resolve that OpenUI should always just use Home/End, and close this issue.

Question (2) seems like its own investigation, outside the scope of the lack of Home/End keys on Mac, that is worth opening a new Issue to track; I agree with @gregwhitworth that this likely needs further research.

Originally posted by @dandclark in #159 (comment)

[gregwhitworth]

This will need more research across UAs and component libs to determine if the events currently defined in the select remain true when the select is both open and closed. This was identified when we found a difference between UAs on different OSes with the home/end keys.

[chrisdholt]

@gregwhitworth traditionally, if I were focused on a button (or other non-select control) and used home/end I would expect to be jumped to the beginning or end of the page as that's the current behavior. As it pertains to select here, I agree that some research is needed to determine what currently happens.

It seems like there is technically a delta in this behavior right now with arrow keys when focused on a native select (example below is Edge). When not focused on select, arrow keys move the page up and down. When focused on a select it opens the popup and changes the selected item. When not focused on a select, home and end move to the top and bottom of the page. When focused on a select, this behavior persists. When the select is open, home/end moves focus between the first and last item.

[una]

There are definitely different events based on state. Rob Dodson has a great video on this concept of "roving focus". I think a table of interaction would be great

[github-actions]

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.