Enhance @layer documentation for clarity and accuracy#44238
Open
kingma-sbw wants to merge 2 commits into
Open
Conversation
Clarified the explanation of the @layer at-rule, emphasizing the precedence of styles and the creation of anonymous layers. Improved the wording for better understanding.
github-actions
Bot
added
Content:CSS
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
|
Preview URLs (1 page) (comment last updated: 2026-05-24 16:15:45) |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Clarified the explanation of the @layer at-rule, emphasizing the precedence of styles and the creation of anonymous layers. Improved the wording for better understanding.
Description
For clarity the order of the descriptions are slightly reordered. Also the three types of
@layerusage is defined more clearly with named sections.Motivation
For clarity and better understanding and exploring the impacts of layering.
Additional details
The original description was not incorrect but a slight change in order and better description and comparison with normal behaviour should make the uscase a bit clearer
Related issues and pull requests