-
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
What's happened with select s ? help-wanted #6647
Comments
Yes I saw it. But should I contact the team somehow ? |
The project is not dead - well this specific one might be but the fork from this one is definitely active and pumping. I have recently applied this update to one of my sites experiencing the exact same issue as you were (which is an IOS issue by the way) and the problems were immediately fixed. If you download the new fork you'll find the select issues are resolved. You can also get some great help here if you need it: https://gitter.im/Dogfalo/materialize |
Great thanks !!! It works !!!! |
Hello, I'm part of the community fork members. As said above, I recommend you to submit issues related to this lib in the community fork (@MaterializeCSS/materialize). If you solved your problem, can you close this issue ? The problem is that we don't have the rights to close issues in this repo, and I sometimes check opened one in order to find problems. |
You can add the class browser-default to get the browser default.
|
Buddy, today I ran into some huge problem in the selectboxes. The selected elements are NOT the ones that I click. For example, if I clicked on an element, I get the 4th element, or if I clicked on option 3, I get the selected element 2. All this applies ONLY to the operation of my site on mobile phones. I have tried more than 10 browsers and more than 15 phone models. Also, EVEN if you open the original site https://materializecss.github.io/materialize/select.html I observe the same problem with selectors .. The problem is. that I have been using materialize for about 5 years in various projects, but this is the first time I have encountered such a pronounced problem .. I'll show you a video if necessary. Please give a comment, what could have happened ? * I am using the version. 1.0.0. * * By the way, I'm in the deal announcing the alpha version 1.1.0 on the website and in the subs... But I don't think that my situation will be solved by updating the version ... I am very much waiting for your answer somewhere, for example in a telegram - @berTalino or in a comment. Thank you very much !
The text was updated successfully, but these errors were encountered: