@@ -178,6 +178,20 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
178178 This may be confusing, since the elements themselves are not necessarily referring to the same object,
179179 but it is a useful model to consider them to be visual states of the same conceptual page entity, that we happen to call "element".
180180
181+ # User-agent keyframes # {#ua-keyframes}
182+
183+ The following <<@keyframes>> are added to the [=user-agent origin=] :
184+
185+ ```css
186+ @keyframes -ua-view-transition-fade-out {
187+ to { opacity: 0; }
188+ }
189+
190+ @keyframes -ua-view-transition-fade-in {
191+ from { opacity: 0; }
192+ }
193+ ```
194+
181195# Pseudo-elements # {#pseudo}
182196
183197 While the UA is [=animating a view transition=] ,
@@ -992,36 +1006,6 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
9921006 <div algorithm>
9931007 To <dfn>animate a view transition</dfn> given a {{ViewTransition}} |transition|:
9941008
995- 1. Generate a <<@keyframes>> named "-ua-view-transition-fade-out" in
996- [=user-agent origin=] as follows:
997-
998- ```css
999- @keyframes -ua-view-transition-fade-out {
1000- to { opacity: 0; }
1001- }
1002- ```
1003-
1004- 1. Generate a <<@keyframes>> named "-ua-view-transition-fade-in" in
1005- [=user-agent origin=] as follows:
1006-
1007- ```css
1008- @keyframes -ua-view-transition-fade-in {
1009- from { opacity: 0; }
1010- }
1011- ```
1012-
1013- 1. Apply the following styles in [=user-agent origin=] :
1014-
1015- ```css
1016- html::view-transition-old(*) {
1017- animation: -ua-view-transition-fade-out 0.25s both;
1018- }
1019-
1020- html::view-transition-new(*) {
1021- animation: -ua-view-transition-fade-in 0.25s both;
1022- }
1023- ```
1024-
10251009 1. [=map/For each=] |name| → |capturedElement| of |transition|'s [=ViewTransition/named elements=] :
10261010
10271011 1. If neither of |capturedElement|'s [=captured element/old image=] or [=captured element/new element=] is null:
0 commit comments