-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add placeholder support to Select #298
Comments
This was initially left off because native Select doesn't support a placeholder. It's easy to add for the custom single-select, but how should it work for native single-select? I think the options are either:
I'm more in favor of (2), since IMO a placeholder shouldn't affect the actual options, but I know a lot of people use (1) as a select placeholder hack |
I vote for leaving out placeholder support for native selects altogether. It's tough to use the span trick reliably across mobile browsers since their UIs are all implemented differently. If we need to support this property for native mode, I vote for option 2. |
I spoke again with @smhigley and we decided placeholder support for custom, non-native Select components makes sense for beta4. |
🚀🚀🚀 |
Enhancement
It would be nice to be able to add a placeholder to Select.
Package Version: latest
Expected behavior:
Actual behavior:
The text was updated successfully, but these errors were encountered: