-
Notifications
You must be signed in to change notification settings - Fork 27
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
Old fashioned html option lists #65
Comments
AFAIK, the Related: #11. |
I always wondered , How come we are not able to customize the view of heavily used select dropdown. This leaves majorly two options.
As you can see , Both the options has cons. Would be better If we get this sorted in some way. |
@rwales1000 We just opened up for Interop 2023 proposals yesterday, see https://github.com/web-platform-tests/interop/blob/main/2023/README.md for the process and what to expect. If you're still interested in proposing this, could you resubmit (or edit) this based on the template we now have? |
Also, from the implementer point-of-view: Safari does support this on macOS today, it will move to the first item matching the string thus far typed. This is likely something we don't really want to standardise, as we likely want to match OS behaviour here to avoid surprising users. When it comes to more complex alternates, there's also work going on around groups such as Open UI with select elements which are more customisable. |
Closing this without prejudice; "If you're still interested in proposing this, could you resubmit (or edit) this based on the template we now have?" still holds. |
Traditional option lists limit the user to typing the first character when selecting. Why not offer type ahead? This would be a major step forwards for this vintage web control.
The text was updated successfully, but these errors were encountered: