[css-view-transitions] Hook into the refresh driver.
Categories
(Core :: CSS Parsing and Computation, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox136 | --- | fixed |
People
(Reporter: emilio, Assigned: boris)
References
(Blocks 1 open bug)
Details
(Whiteboard: [viewtransitions:m1], [wptsync upstream])
Attachments
(1 file)
Once we have the snapshot and pseudo-element machinery, we need to hook the view transitions into the refresh driver code in order to perform the operations at the right time: https://html.spec.whatwg.org/#event-loop-processing-model:perform-pending-transition-operations
|
||
Updated•1 year ago
|
|
Assignee | |
Updated•1 year ago
|
|
|
Assignee | |
Comment 1•1 year ago
|
||
Basically, we have to schedule the performing pending operations after
activating the view transitions, and stop to do that once we don't have
active animations.
There is one known issue: we always timeout even if we activate the view
transitions successfully, so I clear the timeout once we start the animations.
Otherwise, we may always interrupt the long animations whose
durations are longer than dom.viewTransitions.timeout-ms. However, I
guess we may still need a timeout for it. We probably need to figure out
what to do in the future.
Note that /css/css-view-transitions/paused-animation-at-end.html.ini
is failed because we don't have any animations. This is probably blocked by
the dynamic UA stylesheet (Bug 1914324).
Also, update some other tests to avoid getting javascript errors:
JavaScript error: , line 0: uncaught exception: Object.
Description
•