-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Improve "select" #1393
Comments
Well, why do you need to edit the "materialize created" select? you can edit the original select and recreate the materialize one. If the framework allows editing of the "materialize created" select (an styled |
Maybe i mis-use the component, but with meteor, i need to spy the events on the select box and it's not clear how to do that. |
It should work fine in meteor, there are a few open and closed issues regarding this topic. Have a look at #1062 and if that is not helpful you'll be able to find other discussions using the issue tracker search option. |
Hi, the id is specified as data-id to the new input and not erased anymore. |
Closed due inactivity, feel free to reopen it if it is still necessary |
I've played with select input and i'm not satisfied (or i'm mis-using it) :
When i build my select box i set a name and id, but as materialize_select build an input text field, how my JS code can identify this new field ?
It would be cool that this new input can be customized with name and id. We could add data-name and data-id inside the select node, and materialize_select could use it to create the new text field (instead of using the uid generator).
The text was updated successfully, but these errors were encountered: