Skip to content

Commit 9b1bea2

Browse files
committed
broken links
1 parent 6466882 commit 9b1bea2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/content/docs/basics/levels.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,6 @@ But for simple same-document view transitions, there are some highly desirable f
7474
### What Happens when Firefox Releases Level 1
7575

7676
Actually, Firefox Nightly not only supports Level 1 of the View Transition API, but also brings some Level 2 features:
77-
* Firefox Nightly already [has support for `view-transition-class`](https://bsky.app/profile/vtbag.dev/post/3ltwvggp7xc2u) and the [`:active-view-transition` pseudo-class](basics/test-page/).
77+
* Firefox Nightly already [has support for `view-transition-class`](https://bsky.app/profile/vtbag.dev/post/3ltwvggp7xc2u) and the [`:active-view-transition` pseudo-class](/basics/test-page/).
7878
* Firefox Nightly already [has support for `view-transition-name: match-element`](https://bsky.app/profile/martr.app/post/3lwyzve7nac2i), but not for `view-transition-name: auto`, which is not really part of the standard. When usings the [declarative-names script](/tools/utensil-drawer/#declarative-names) from The Bag's Utensil Drawer, you also have an alternative for dynamically generating view transition names that works more reliably across browsers.
7979
* So the main problem might be the missing support for view transition types. Good news here: The Bag's Utensil Drawer now has a [polyfill for view transition types](/tools/utensil-drawer/#usetypespolyfill-always--never) to support them even on browsers that only implement Level 1 of the View Transition API!

0 commit comments

Comments
 (0)