-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Tweak <aside> conditional mappings to check for more cases #43013
Merged
cookiecrook
merged 7 commits into
web-platform-tests:master
from
sivakusayan:nested-aside-manual-role
Feb 3, 2024
Merged
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
7adb584
Add contextual role case for <aside> in <main> element
sivakusayan 506ac5a
Add case for section in <main>
sivakusayan bf4e7b9
Naming changes
sivakusayan e5e4904
Check aside mapping for all sectioning content
sivakusayan 5bf06f8
Merge branch 'master' into nested-aside-manual-role
sivakusayan 3aacf09
Fix test name from merge
sivakusayan fb5e299
Only assert conditional aside mappings for named sections
sivakusayan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noting that while this is what the spec currently says to do, because the section is without a name it is treated no differently than a
div
in the accTree.but if that section were given a name, then it would be a role=region, and then it would would be more appropriate for this to be generic.
https://github.com/w3c/html-aam/pull/484/files will eventually address this, but mentioning it here if we want to do anything about it now / modify html aam to at least rectify this single case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to name the
<sections>
in this WPT change and to ignore the un-named<section>
case until w3c/html-aam#484 is merged? That way, browsers that are following to the spec word-for-word aren't dinged yet, but browsers that eagerly implement the behavior in w3c/html-aam#484 can still pass the WPT.Alternatively, we could include the un-named
<section>
case here and assert that:if people are okay with it, but I don't know if people feel weird about WPT tests that aren't formally in the spec yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is general agreement to the spec change and no objection, I think it's fine to merge the test.
ARIA WG Chairs changed the process so it's now the expectation that any spec change PR will be approved, but not merged until there are 1. tests, and 2. multiple passing implementations. So if we didn't merge the test, it would cause a circular dependency with the spec PR. 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if you two have fully resolved this thread, but the rest of the PR looks good to me, so I'm approving.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that w3c/html-aam#484 still seems to be under discussion, so I ended up doing the half measure of just naming the
<section>
in this PR, while ignoring the un-named<section>
case. We can always refine these tests as needed once people seem to come into an agreement there.