Clarifications for HTML's autocomplete and aria-autocomplete #2350
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
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
MelSumner
reviewed
Oct 18, 2024
MelSumner
approved these changes
Oct 18, 2024
thank you @MelSumner. Co-authored-by: Melanie Sumner <[email protected]>
cookiecrook
approved these changes
Nov 15, 2024
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.
Closes #2337
autocompletemapping for theformelement (it doesn't map directly to the form element, but rather owned form controls will expose a supports autocompletion mapping, or not).aria-autocomplete=" [ valid value ] "andautocomplete=offtogether, but that forautocomplete=" [ valid value ] "andaria-autocomplete="[ valid value ] ", UA behavior should win out.not sure how much more detail needs to be provided, as attempting to do so felt like treading into repeating what is already defined in each spec for these attributes (html / aria).
Test, Documentation and Implementation tracking
Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.