Skip to content

Commit c5b864c

Browse files
authored
Undo two-phase explainer edit
1 parent b1fa799 commit c5b864c

File tree

1 file changed

+2
-13
lines changed

1 file changed

+2
-13
lines changed

css-view-transitions-2/two-phase-transition-explainer.md

Lines changed: 2 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -91,21 +91,10 @@ Specifically, the `addRestoreCallback` mechanism can be easily overlooked by dev
9191
As an alternative, proposing a declarative CSS-based solution, based on view-transition at rules and `@navigation` conditionals:
9292

9393
```css
94-
@navigation(preview: active) {
94+
@navigation(preview) {
9595
#skeleton {
9696
display: block;
9797
}
98-
99-
::view-transition-group(*) {
100-
animation-iteration-count: infinite;
101-
}
102-
}
103-
104-
@navigation(preview: exiting) {
105-
::view-transition-group(*) {
106-
/* this would stop the infinite animation, letting it complete */
107-
animation-iteration-count: 1;
108-
}
10998
}
11099

111100
@view-transition {
@@ -115,7 +104,7 @@ As an alternative, proposing a declarative CSS-based solution, based on view-tra
115104
```
116105

117106
The "preview" animation with its attached types would start when the navigation is initiated (but not intercepted), and would defer the commit until
118-
it is finished. The "new" state of the animation would be controlled by style only, using the `@navigation(preview: active)` conditional (which can be mixed and matches with other conditionals).
107+
it is finished. The "new" state of the animation would be controlled by style only, using the `@navigation(preview)` conditional (which can be mixed and matches with other conditionals).
119108

120109
## Pros and cons of the different solutions
121110

0 commit comments

Comments
 (0)