Skip to content
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

Standardise and expose browser pickers #922

Open
lukewarlow opened this issue Oct 31, 2023 · 5 comments
Open

Standardise and expose browser pickers #922

lukewarlow opened this issue Oct 31, 2023 · 5 comments
Labels
discussion Thoughts and opinions wanted stale

Comments

@lukewarlow
Copy link
Collaborator

lukewarlow commented Oct 31, 2023

There's requests to improve various inputs #421 #423

Most of these requests actually apply to the "pickers" more so than the trigger input (though that should be addressed too).

Currently browsers all expose picker UIs for a variety of input types. e.g. color, and date. It's inconsistent which inputs get these pickers exposed and how they look. There's also use cases that aren't addressed such as range support.

On native platforms (such as macOS) there's the ability to have for example a date input, but then also the graphical "picker" these can be used separately.

Is it worth OpenUI looking into standardising these pickers in a way that also makes them usable standalone (much like listbox is the selectlist picker but is usable standalone?).

(File picker I suggest we leave alone as that's quite a standard at this point and very security conscious)

@lukewarlow lukewarlow added the discussion Thoughts and opinions wanted label Oct 31, 2023
@lukewarlow
Copy link
Collaborator Author

This should be even easier now we have popover and soon anchor positioning as I imagine (at least Chrome and Firefox) will move to a web implementation for their picker UIs.

@lukewarlow
Copy link
Collaborator Author

This came out of whatwg/html#9754 (comment) which suggests a key use case developers wanted showPicker for was to be able to get the pickers even if the input isn't in the DOM.

I feel like we'd be better off allowing them to just use the pickers as elements rather than using hacks such as that (especially because implementations aren't consistent and positioning is currently impossible)

@YummyBacon5
Copy link
Contributor

How would this work? Would the UA's browser picker be embedded into the page? - since on mobile browsers, it's normally a picker that stops interaction with the rest of the page

Or would it be a custom picker that authors could create with elements.

@lukewarlow
Copy link
Collaborator Author

Would need discussion but I'm leaning towards making a touch friendly web based picker UI and using that everywhere. So a standardised version effectively.

Copy link

github-actions bot commented May 1, 2024

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.

@github-actions github-actions bot added the stale label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Thoughts and opinions wanted stale
Projects
None yet
Development

No branches or pull requests

2 participants