How to avoid problems with Turbo morphing | Radan Skorić's website

Turbo 8 debuted a new page refresh approach: morphing. For the rest of the article I’m going to assume you are familiar with it. Like other Rails “magic”, morphing delights when it works and frustrates when it interferes. And its interference can be extremely annoying. Common problems include: Non-Turbo-aware JavaScript libraries lose their initialized DOM elements during morphing. User-modified UI states (opened sidebars, accordion elements) reset to defaults. Server-loaded forms disappear after morphing. These issues share one root cause: Part of the new state is in the browser and morphing causes problems by forcing it to match server state.