-
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
Select component passed to Vanilla JS. Handle options and normally fix all known issues. #2670
Conversation
Do you have any date for this to be available? |
Hi, I got no response since the PR so for now I just wait like the 166 others. |
Don't get me wrong Tyrion, I was just asking because this is great, and was hoping to use this on my website as soon as is available. |
If you want to use it you can modify the component modified in the PR. |
Can you confirm that the 'onchange' listener for select objects is working? |
Closed because no response in 1 month. |
Sad.. Looks like a great fix. |
@Thanood Thanks, but you can load an overload file if you really want to use it. I encourage anyone to see this message repository to drop it because it is not maintained properly and errors stack every day without anything being done, at least not fast enough. They could organize their pull request or just give an answer but they are choosing to remain silent, to me it's disrespectful. |
@badaro42 Sorry, I'm just seeing your comment right now, I provide a fix on my fork. But I don't know that will be useful now. |
Ah.. I didn't see this. Actually, we could just use your version of MaterializeCSS from your master branch right? |
Yes it should works but if you encounter an issue don't hesitate to report it, I'll fix. |
It's a shame they chose to ignore your PR. I'll checkout your version and take a look. Thanks @TyrionGraphiste |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TyrionGraphiste Would you move the changes that you made to the forms.html to the jade file in /jade/page-contents ? And why did you edit the dropdown.js ? I thought just rewrote the select plugin?
It is a closed PR. I won't ever work for this repo. |
Hi everyone,
Related to #2514, I rebase this PR passing to Vanilla JS for being less complicated.
So, this PR should fix all these issues :
#2274
#1707
#1296
#2535
#2522
#2548
#2554
#2536
#2436
#2522
#2652
#2602
#2575
#2285
#1638
#1393
#1077
#2402
This issue can't be fixed, because this is a browser bug and it's seems we can't do anything for now but wait for a fix : #2448
The PR allow now some options like :
I updated the documentation for being more understandable, so now you can init a select like this :
For init with options:
For init :
For destroy :
There is now some calls for update the select instead of destroy and recreate it :
So, select is using now some same functionalities of the dropdown component, feel free to match the remaining options like induration, outduration, constrainWidth, gutter and alignement.
This PR adds the possibility to use optgroups with Materialize Multiple Select, there is some working example :
https://jsfiddle.net/TyrionGraphiste/5deezjj0/1/
The code passed to Vanilla JS, so it's possible than some people encounter errors because I don't use polyfill. As mentionned in #2522 the polyfills should be global and accessible from each component, however it will give a real bad code if every component has its own polyfill and sometime the same several times.
One last thing, Jasmine tests should be updated because some changes.
Hope it will fix all issues we are encounter with this component.