-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Input type should be honored (e.g. email, url, tel) #149
Comments
I agree that this would be nice. It's a bit more complicated than transferring the attribute to the the inner textbox, though. When allowing users to create options on the fly, there will have to be checks in place to ensure that input text is valid before adding the option. In the cases that it's not valid, it should trip up native validation errors in the browser (related article). Also, we shouldn't really support one type without supporting the others: <input type="email">
<input type="url">
<input type="tel"> |
I'm not familiar with the standard/implementation but those features don't seem mutually exclusive.
Agreed. I've updated the description. Feel free to add any other types. |
+1. Especially for the type="email". perhaps using a input pattern may helps solve the issue. Also having the correct input type would help bring up the correct keyboard type (regular vs email vs number) on smartphones and tablets. |
Input type email support is another issue. Only types suporting selection can be used (https://html.spec.whatwg.org/multipage/forms.html#do-not-apply). So issue would be that get selectize to work withiout using selection functions. |
closing stale issues older than one year. |
When setting an input type to
email
, for example, it should pass through to the input that selectize creates.This is handy for mobile devices as the type is how they determine what keyboard to display.
Other fields such as
url
andtel
should also work.The text was updated successfully, but these errors were encountered: