#530@minor: Broader support for HTMLLabelElement control.
#987
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This supports nested / descendent input elements for HTMLLabelElement's `control` property and also supports other labelable elements, as described in the spec: https://html.spec.whatwg.org/multipage/forms.html#category-label To be fully spec-compliant, the `control` getter would ignore `for` element(s) that aren't labelable elements, and labelable elements would also include form-associated custom elements. I'm using a CSS selector for this, because that seemed like the most convenient approach, but if another approach would be better (e.g., for performance?), please let me know. Fixes #530.
capricorn86
approved these changes
Aug 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This supports nested / descendent input elements for HTMLLabelElement's
controlproperty and also supports other labelable elements, as described in the spec:https://html.spec.whatwg.org/multipage/forms.html#category-label
To be fully spec-compliant, the
controlgetter would ignoreforelement(s) that aren't labelable elements, and labelable elements would also include form-associated custom elements.I'm using a CSS selector for this, because that seemed like the most convenient approach, but if another approach would be better (e.g., for performance?), please let me know.
Fixes #530.