You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/content/docs/challenges/angular/44-view-transition.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,16 +12,16 @@ sidebar:
12
12
## Information
13
13
14
14
The View Transition API is a brand new API that provides a set of features that allow developers to control and manipulate the transitions and animations between views within an application.
15
-
It plays a pivotal role in enhancing user experience (UX), bringing applications to life with engaging and captivating transitions to guide users through different pages or sections of the app.
15
+
It plays a pivotal role in enhancing the user experience (UX), bringing applications to life with engaging and captivating transitions to guide users through different pages or sections of the app.
16
16
17
17
The goal of this challenge is to learn about and manipulate all types of transitions proposed by the API.
18
18
19
19
To use the API, Angular provides a function `withViewTransitions()` that needs to be injected inside the router config.
20
20
21
-
I would advise you to read the [Chrome documentation](https://developer.chrome.com/docs/web-platform/view-transitions). You will learn everything necessary to successfully complete the challenge.
21
+
I would advise you to read the [Chrome documentation](https://developer.chrome.com/docs/web-platform/view-transitions). You will learn everything that is necessary to successfully complete the challenge.
22
22
23
23
Here, however, is a short summary:
24
-
Firstly, each target DOM element has two states; an `old` one when the element is leaving the page, and a `new` one when it's entering the page:
24
+
Firstly, each target DOM element has two states: an `old` one when the element is leaving the page, and a `new` one when it's entering the page:
25
25
26
26
```css
27
27
::view-transition-old(root) {
@@ -46,7 +46,7 @@ This allows you to create an animation for this element only.
46
46
Lastly, if the same element is present in both views, you can automate the transition by assigning the same **transition name**.
47
47
48
48
:::danger
49
-
Remenber, you can have only ONE UNIQUE `view-transition-name` per page.
49
+
Remember, you can have only ONE UNIQUE `view-transition-name` per page.
50
50
:::
51
51
52
52
## Statement
@@ -63,12 +63,12 @@ To the final state shown in the following video:
63
63
64
64
Observe the following:
65
65
66
-
- The header slides in and out
67
-
- Each element smoothly transitions to its new location
66
+
- The header slides in and out.
67
+
- Each element smoothly transitions to its new location.
68
68
69
69
### Level 1
70
70
71
-
Focus only on the first thumbnail and create a seamless and pleasing transition
71
+
Focus only on the first thumbnail and create a seamless and pleasing transition.
0 commit comments