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: src/content/docs/tips/view-transition-fails-and-fixes.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ or [opening an issue on GitHub!](https://github.com/vtbag/website/issues/new?tem
44
44
45
45
#### Potential Pitfall: Unreliable Detection of the Opt-in
46
46
47
-
Aparticularly pitfall occurs when the `@view-transition` at-rule is present but not reliably detected by the browser. This can happen in Chrome, for example, when the at-rule is placed in an external stylesheet after tons of other CSS.
47
+
Aparticular pitfall occurs when the `@view-transition` at-rule is present but not reliably detected by the browser. This can happen in Chrome, for example, when the at-rule is placed in an external stylesheet after tons of other CSS.
48
48
49
49
According to the specification, the check for `@view-transition { navigation: auto }` happens together with the `pagereveal` event just before the first rendering. In theory, that means the browser should wait for render blocking resources such as external stylesheets linked in the `<head>`. However, Chrome may perform this check [without necessarily waiting for external CSS](https://issues.chromium.org/issues/383014860#comment9).
0 commit comments