Turbo View Transitions

[Turbo][] plugin to use View Transitions API. This plugin allows you to animate transitions of specific elements between pages by adding data-turbo-transition attribute to them.

> [!NOTE]
> Although this library named after Turbo, it can be used with any other HTML-driven application. See, for example, how we use it with Docsify for docs.anycable.io.

Usage

The primary goal of this library is to allow animated _objects_ on the page in HTML driven applications. When you have a _collection page_ and a _single object_ page and want to animate the transition between them, you can hit the following problem: there cannot be multiple elements with the same view-transition-name style defined on the page. To overcome this limitation, this library helps to identify matching elements and add the view-transition-name style on-the-fly and only for the duration of the transition. All you need is to add a data-turbo-transition="" attribute to the elements you want to animate.

$3

Here is how you can use this plugin to animate Turbo (v7) navigation with View Trantisions:

``js
import { shouldPerformTransition, performTransition } from "turbo-view-transitions";

document.addEventListener("turbo:before-render", (event) => {
if (shouldPerformTransition()) {
event.preventDefault();

performTransition(document.body, event.detail.newBody, async () => {
await event.detail.resume();
});
}
});

document.addEventListener("turbo:load", () => {
// View Transitions don't play nicely with Turbo cache
if (shouldPerformTransition()) Turbo.cache.exemptPageFromCache();
});
`

> See Turbo Music Drive application for a full-featured example.

$3

#### shouldPeformTransition

This function returns true iff both of the following conditions are satisfied:

- document.startViewTransition function is defined.
- element is present on the page. This meta is used to control whether the transition should be performed or not.

Use this function to check if the transitions are going to be performed or not.

#### performTransition

This is the main interface of this library. It's a wrapper over document.startViewTransition function which marks matching elements from _before_ and _after_ states with the view-transition-name: ... style to activate object transitions (see the Turbo example above).

This function requires you to provide old and new HTML elements as well as the callback function which responsible for the actual HTML update:

`js
const oldEl = document.body;
const newEl = document.createElement('body');
newEl.innerHTML = '<...some html from wherever...>';

performTransition(oldEl, newEl, () => {
// Update the DOM
document.body.replaceWith(newEl);
});
`

The elements with the data-turbo-transition attributes will be matched, and the corresponding view-transition-name style will be applied to them according to the following rules:

- If the value of the data-turbo-transition attribute is non-empty then it will be used as the value of the view-transition-name style.
- If the value of the data-turbo-transition attribute is empty then the view-transition-name will be equal to the "$" + (el.id || "0").
- The view-transition-name is only added to elements if they are present in both old and new HTML (and have the same transition name if it's specified).
- If there are multiple elements with the same view-transition-name present in the old or new HTML then the none will be activated (i.e., the view-transition-name style won't be added to them).
- During the transition, the data-turbo-transition-active attribute is added to all activated elements (so you can use it to style them).

You can customize attribute names used to identify and mark elements by passing the options object as the last argument:

`js
performTransition(oldEl, newEl, () => {
// Update the DOM
document.body.replaceWith(newEl);
}, {
transitionAttr: 'data-view-transition',
activeAttr: 'data-active-view-transition',
});
``

[Turbo]: https://turbo.hotwire.dev/