Skip to content

[css-cascade-5] page and view-transition at rules should cascade #9604

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[css-cascade-5] page and view-transition at rules should cascade #9604

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
[css-cascade-5] page and view-transition at rules should cascade
  • Loading branch information
@noamr
noamr committed Nov 16, 2023
commit 92aa1bb7a448c84fd70bf5a027b2e35482b7d8b3
5 changes: 5 additions & 0 deletions css-cascade-5/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1253,6 +1253,11 @@ Cascade Layers</h3>
that are defined inside [=cascade layers=]
also use the layer order when resolving name collisions.

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=].
Copy link
Contributor

@mirisuzanne mirisuzanne Nov 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


<div class="example">
For example,
authors could override the animation from a framework,
Expand Down