LibWeb: Add handling for view transition selector specificity #6126
Conversation
|
Hello! One or more of the commit messages in this PR do not match the Ladybird code submission policy, please check the |
The corresponding WPT test was not imported since it still fails for unrelated reasons. As it stands right now, we have no way of testing this behavior.
Psychpsyo
force-pushed
the
vt-selector-specificity
branch
from
80854dd to
2d17010
Compare
Psychpsyo
changed the title
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions! |
| if (first_is_one_of(simple_selector.pseudo_element().type(), CSS::PseudoElement::ViewTransitionGroup, CSS::PseudoElement::ViewTransitionImagePair, CSS::PseudoElement::ViewTransitionOld, CSS::PseudoElement::ViewTransitionNew) && simple_selector.pseudo_element().pt_name_selector().is_universal) | ||
| break; | ||
|
|
||
| // otherwise just count the number of type selectors and pseudo-elements in the selector (= C) |
There was a problem hiding this comment.
This was actually a spec comment, it just doesn't look like it.
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions! |
|
This pull request has been closed because it has not had recent activity. Feel free to open a new pull request if you wish to still contribute these changes. Thank you for your contributions! |
3 participants
The corresponding WPT test was not imported since it still fails for unrelated reasons.
As it stands right now, we have no way of testing this behavior.