-
Notifications
You must be signed in to change notification settings - Fork 605
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
optgroup does not work when some options are nested and some are not #615
Comments
Hello @mtriff, can you take a look at this bug eventually please ? 😭 |
I have started to look into this, but didn't get very far yet. I do have a failing cypress test though, if anyone wants to support: https://github.com/voidus/Choices/tree/fix-mixed-optgroups Next step: Find the relevant place in the code |
Okay I've oriented myself a bit in the code and found an approach. Right now, afaict, the parts that process the options deal with either TBH, I was expecting the change on the branch to already have an effect, but it doesn't look like it. @mtriff would you be generally open to merge something like this? Otherwise we should probably discuss potential approaches. (Tagging you because you seem to be maintaining the repo) |
Closes Choices-js#615. This pushes the conversion of OPTION/OPTGROUP elements to Choice objects into the WrappedSelect class and unifies the code paths a little between groups-present and groups-not-present. Some work towards possibly fixing Choices-js#615
Closes Choices-js#615. This pushes the conversion of OPTION/OPTGROUP elements to Choice objects into the WrappedSelect class and unifies the code paths a little between groups-present and groups-not-present. Some work towards possibly fixing Choices-js#615
Yeah folks I think I got it. 🕺 |
The library used works if every
<option>
is in a<optgroup>
but has a bug when some are nested and some are not.This will work:
This will not:
Related: #253
The text was updated successfully, but these errors were encountered: