Clarify mappings for contenteditable #463
Merged
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
Per discussion around the minimum role concept, and the WG deciding that contentedtiable should remain unmapped to any specific ARIA role when used on a generic. per that decision #324 is closed, but the other clarifications that were to be a part of that PR are now in this one. Additionally, there are other necessary updates needed for these mappings, as the previous ones did not get into the nuance of how to handle nested `contenteditable` attributes.
jnurthen
requested review from
aleventhal,
jcsteh and
cookiecrook
and removed request for
cookiecrook
jcsteh
approved these changes
Mar 10, 2023
|
My review was requested in an ARIA meeting, but since the substantive changes are all related to Windows and Linux API, I'm removing myself as a reviewer. |
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.
Per discussion around the minimum role concept, and the WG deciding that contentedtiable should remain unmapped to any specific ARIA role when used on a generic. per that decision #324 is closed, but the other clarifications that were to be a part of that PR are now in this one.
Additionally, there are other necessary updates needed for these mappings, as the previous ones did not get into the nuance of how to handle nested
contenteditableattributes.This PR does not include changes for
contenteditable=plaintext-only(though there is some commented out text which does mention this state). Mappings forplaintext-onlywill be included in, or be a follow-on to #454.plaintext-onlylanded in HTML - whatwg/html#8275Preview | Diff