-
Notifications
You must be signed in to change notification settings - Fork 199
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
Should <input type=file> have an open state? #181
Comments
I think an "open" state could be interesting. In addition to the consistency points raised in the PR, one could add unfocus styles to your UI while the user has this open. Would we also want this for the color input type? |
I think it makes sense for all inputs that feature some kind of "open" state - agreed @una. And yes, I'm also interested in the styling opportunities this provides. |
This was discussed in the 11/5 telecon and we resolved on yes for both the file input and any control/component that opens a picker/popup type container.
|
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. |
This issue comes from this comment: https://github.com/WICG/open-ui/pull/140/files#r468264056
Today, browsers open the system's file picker which blocks user interaction with the window until a selection is made, or the action is cancelled. This may not always be the cases, and for consistency with
<select>
, it might make sense to add anopen
state to this input.An
open
state would also allow for further design customisations.The text was updated successfully, but these errors were encountered: