CustomStateSet doc: Add feature detection for :state pseudo-class and browser compatibility warning #33656
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
|
Preview URLs (comment last updated: 2024-05-17 10:01:36) |
minimalsm
commented
May 17, 2024
minimalsm
commented
May 17, 2024
minimalsm
commented
May 17, 2024
minimalsm
commented
May 17, 2024
github-actions
bot
added
size/m
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
minimalsm
changed the title
sideshowbarker
approved these changes
May 19, 2024
|
Thank you. |
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.
Description
Added feature detection for the :state CSS pseudo-class and provided a warning message if the browser does not support this syntax.
Motivation
The current syntax isn't supported in Chrome browsers yet, and although Chrome 125 is adding support, there will be a transition period where I suspect the majority of readers will be using an incompatible browser.
Additional details
Per @hamishwillee's comment in 33636:
Related issues and pull requests