In css-view-transitions-2, we're adding :active-view-transition pseudo-class that activates on the html element when a view transition is happening. It also takes some parameters. Some examples are below:
/* matches for any view transition */
html:active-view-transition(*) { ... }
/* matches a view transition that has "foo" as one of the types specified */
html:active-view-transition(foo) { ... }
/* matches a view transition that has any of the following in the types: "foo", "bar", or "baz" */
html:active-view-transition(foo, bar, baz) { ... }
This issue is about what specificity this should have.
My proposal is that specificity of :active-view-transition(*) is pseudo-class-like (a.k.a. B) and :active-view-transition with any other parameter(s) is twice pseudo-class-like.
The justification here is that specifying a parameter seems more specific, but increasing the number of parameters doesn't change specificity since it's a disjunction of types.
In css-view-transitions-2, we're adding
:active-view-transitionpseudo-class that activates on thehtmlelement when a view transition is happening. It also takes some parameters. Some examples are below:This issue is about what specificity this should have.
My proposal is that specificity of
:active-view-transition(*)is pseudo-class-like (a.k.a. B) and:active-view-transitionwith any other parameter(s) is twice pseudo-class-like.The justification here is that specifying a parameter seems more specific, but increasing the number of parameters doesn't change specificity since it's a disjunction of types.