-
Notifications
You must be signed in to change notification settings - Fork 150
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
toggling @disabled on the next select actually toggles it on its children options #558
Comments
8549
changed the title
toggling @disabled on the next <select/> actually toggles it on its children options
toggling @disabled on the next select actually toggles it on its children options
Aug 8, 2024
I debugged the script execution and found that the culprit is in the implementation of Runtime.forEach() _hyperscript/src/_hyperscript.js Lines 1530 to 1544 in 1e65fb1
the HTMLSelectElement which is passed as value is considered an iterable so the wrong else-if branch is executed (and the toggle command is executed on the select's iterables -- its children options!) instead of the default (call once func on value). |
I currently have the same problem. Did you happen to find a workaround for this? |
@sanchawebo The dev confirmed that he's going to fix this issue in September: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code to reproduce (tested in playground):
Issue persists even by addressing the select with an id or by targeting
the parentElement of the next <option/>
.The text was updated successfully, but these errors were encountered: