-
Notifications
You must be signed in to change notification settings - Fork 126
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
Consider allowing combobox to open menus #2050
Comments
This would at least correct how Chrome submits a native HTML select element to the API: as a combobox with menu and menuitem. And it would be closer to the iOS implementation, where the select is rendered as a menu button. |
For a concrete example of this in the wild, the current Fluent UI multiselect combobox opens a menu with The primary reason for this was that it performed markedly better than listbox/option for multiselect scenarios in a user study. |
Discussed in today's working group meeting: https://www.w3.org/2023/10/19-aria-minutes.html#t06 Next steps: @mcking65 to make a PR with the change in the title, @scottaohara to make follow up issues for the other points discussed |
closes #2050 This PR simply adds `menu` to the paragraph of text that indicates what value needs to be used for the aria-haspopup attribute, if the popup is not a listbox: >authors MUST specify an aria-haspopup value of tree, grid, or dialog that corresponds to the role of its popup. I think some additional text could be written in the `menu` role definition to further acknowledge this new allowance. But I'll leave that open for discussion, rather than immediately start adding such text.
This is being asked for consideration for a few reasons:
The text was updated successfully, but these errors were encountered: