-
-
Notifications
You must be signed in to change notification settings - Fork 96
Fix multiple choice click capturing #1560
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
base: main
Are you sure you want to change the base?
Conversation
Different quizzes in the same page apparently share the same ID space for labels, even though they're in separate shadow roots. Fortunately, the `<input>` tags are nested inside the `<label>` tags, so the `for` attribute isn't necessary, they implicitly bind to their contained tag. So removing the `for` attribute here preserves the desired behaviour, while removing the confusion of which element is being targeted.
✅ Deploy Preview for cyf-programming ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-piscine ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-sdc ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-launch ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-common ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-tracks ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-itd ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
What does this change?
Different quizzes in the same page apparently share the same ID space for labels, even though they're in separate shadow roots.
Fortunately, the
<input>
tags are nested inside the<label>
tags, so thefor
attribute isn't necessary, they implicitly bind to their contained tag.So removing the
for
attribute here preserves the desired behaviour, while removing the confusion of which element is being targeted.Common Theme?
common-theme/layouts/partials/multiple-choice.html
Fixes #1410