Topic: materialSelect and id with colons(s)
Hi,
it seems that material select cannot handle ids containing colons. This is a know jquery issue but can be solved by escaping the colon. Looks like the materialSelect does not do proper escaping.
Expected behavior Select Options are shown.
Actual behavior Select Options are not shown when the id of the select contains a colon.
Resources (screenshots, code snippets etc.)
This does not work:
<select id="foo:bar" name="foo:bar" class="mdb-select md-form" size="1"> ...
Seems that the code cannot handle the generated id of ul
<ul id="select-options-foo:bar" class="dropdown-content select-dropdown w-100 " style="display: none;">
...
</ul>
This is a major issue for us. Thanks and kind regards,
Oliver
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Status
Open
Specification of the issue
- User: Pro
- Premium support: No
- Technology: MDB jQuery
- MDB Version: 4.14.1
- Device: Desktop
- Browser: Firefox / All
- OS: All
- Provided sample code: No
- Provided link: No
Tags
Related topics
Mateusz Łubianka staff commented 5 years ago
Hi @lgkk,
Ok, I see the problem. I will create a task with this topic, our team will discuss the solution to this problem. Thank you for reporting this issue.
Best,
lgkk pro premium commented 5 years ago
Hi,
thanks, do you have a rough guess about how long it will take to fix the issue? General question: ist it possible that other components also have issues with ids containing colons?
Kind regards
Mateusz Łubianka staff commented 5 years ago
Hi, It's possible because we use jquery in every component code. I can't give you the exact date right now because our team needs to discuss the solution of the problem.
Best,
lgkk pro premium commented 4 years ago
Hi, any news on this issue? We are using v4.14. Is it already solved in a newer release? As a Pro User it would be nice to get some feedback. Thx, regards.
Grzegorz Bujański staff commented 4 years ago
Hi, I'm sorry but unfortunately this has not been fixed yet.