[css-cascade-5] page and view-transition at rules should cascade #9604
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
mirisuzanne
reviewed
Nov 16, 2023
| Other [=at-rules=] which rely on [=cascading=] | ||
| such as ''@page'' or ''@view-transition'' | ||
| that are defined inside [=cascade layers=] | ||
| also use the layer order when determining order and [=specificity=]. |
There was a problem hiding this comment.
Specificity only applies to selectors. Maybe 'priority' or 'cascade priority' would make sense here? I'd defer to Elika on the best way to phrase this.
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.
Mention that
@view-transitionand@pageat-rules respect CSS layer when computing order/specificity.Closes #9601