Add feature for focusable display: contents
elements
#24766
Merged
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.
Summary
Add a feature representing a specification change, where descendants of
display: contents
must be accessible.Test results and supporting details
display: contents
has severe accessibility issues (for example). It's difficult for web-features to generate a status fordisplay: contents
without data reflecting this fact. This PR attempts to add the data needed to accurately report support fordisplay: contents
in a non-surprising way.Admittedly, this is a weird feature. No browser has actually shipped this "feature" yet, though there's work in progress in Chrome (Chrome Platform Status; intent to ship) and it's an Interop 2024 selection.
Alternatives considered:
Representing this as a
partial_implementation
oncss.properties.display.contents
itself. Advantages include more aggressively warning developers about the seriousness ofdisplay: contents
as it is currently implemented. The disadvantages include trying to communicate a rather large thing as an unstructured note and that it would (wrongly) imply that browsers have implementeddisplay: contents
incorrectly or non-interoperably, when it was the spec that changed.Representing this inversely as a deprecated feature (e.g.,
css.properties.display.contents.unfocusable_elements
). This has a maintenance advantage: you get to remove this feature as irrelevant in a few years, after everyone has "removed" the old behavior. This has the disadvantage of implying that browsers have shipped some extra behavior, not that the behavior is, strictly speaking, wrong.Links
css/css-display/focus/display-contents-focus.html
on wpt.fyidisplay: contents
accessibility web-platform-tests/interop#568Related issues