-
There are a couple of patterns where an element's position from the old state needs to be retained and animated but not its content. For example:
1. The user clicks a playing video which then anima…
-
-
CSS Pseudo spec defines [tree-abiding pseudo-elements](https://www.w3.org/TR/css-pseudo-4/#treelike) which are pseudo-elements that fit in the box tree like DOM elements. All of the view-transition ps…
-
Follow up on #10334 (nested transitions)
It's clear what happens when both the old and new state have the same `view-transition-group`.
We need to specify, however what happens when there is a mis…
-
Following up on #8282:
Currently to set a style that behaves differently based on whether the element is in the viewport, one has to use scroll-driven animations. For example, to set a `view-transiti…
noamr updated
1 month ago
-
Chrome has added support for the `display` property and work to add similar support in WebKit is ongoing ([bug 267762](https://bugs.webkit.org/show_bug.cgi?id=267762)). As part of this work, I noticed…
-
The WA-API allows targeting pseudo elements originating from a DOM element using `pseudoElement` in `KeyframeEffectOptions`. See the following description in the spec [here](https://drafts.csswg.org/w…
-
Hi, pseudo elements aren't being synced because the event's target is the real element with another prop called pseudoElement to indicate what really is triggering the animation.
![image](https://u…
-
### Describe the project you are working on
I am working on a 2D card game, which requires creating a series of card-related movement animations.
### Describe the problem or limitation you are h…
mnikn updated
3 weeks ago
-
For view transitions, right now we take snapshots for the old & new state and they get rendered in the `::view-transition-{old|new}` pseudo elements as the contents. But what if we could access those …
noamr updated
1 month ago