-
Notifications
You must be signed in to change notification settings - Fork 201
Adds display: contents #1966
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
Adds display: contents #1966
Conversation
|
@captainbrosset I saw your comment on the other PR (#1131). How does this look to you? |
Co-authored-by: Patrick Brosset <patrickbrosset@gmail.com>
ddbeck
left a comment
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've made some suggestions to handle the accessibility issue. This is still blocked until the next BCD release, even if these suggestions are resolved.
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
|
@vwallen I just merged the latest BCD, so |
Co-authored-by: Patrick Brosset <patrickbrosset@gmail.com> Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
This would replace an existing draft PR that appears inactive: #1131
The support story here is messy: BCD shows high support, but Can I Use shows partial support across the board due to buggy implementations or significant accessibility problems (for example, removing
<button>elements from focus navigation).The
css.properties.display.contents.contents_unusualrefers to default behavior for elements wheredisplay: contentswould result in incomplete, non-semantic, or non-nonsensical behavior. This part of the spec doesn't provide any guidance as to how this should affect accessibility.Closes #1131.