Skip to content
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

contextual role invalidations tests #20

Closed
Tracked by #3
cookiecrook opened this issue Mar 11, 2023 · 2 comments · Fixed by web-platform-tests/wpt#42412
Closed
Tracked by #3

contextual role invalidations tests #20

cookiecrook opened this issue Mar 11, 2023 · 2 comments · Fixed by web-platform-tests/wpt#42412
Assignees

Comments

@cookiecrook
Copy link
Collaborator

cookiecrook commented Mar 11, 2023

contextual role invalidations like orphaned roles outside their required context like a cell outside a table <div role="cell"> -> "undefined" (the resulting roles may be underspecified in some cases, so there may be implementation differences)

follow-on from #8

@cookiecrook
Copy link
Collaborator Author

cookiecrook commented Mar 20, 2023

In WPT PR 38925 (comment) @spectranaut mentioned this special case, which may apply to this issue:

Footer has different HTML-AAM mappings when in the context of main or not. Internally, Chrome uses the roles "FooterAsNonLandmark" and "Footer" to represent the difference (codepen example). I'd guess that WebKit doesn't need to have this distinction internally, though I'm not sure?

@rahimabdi
Copy link

@cookiecrook Self-assigning this one as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants