- Issue created by @ambient.impact
-
Ambient.Impact →
committed ded69cc4 on 2.x
Issue #3411449: Disabled Turbo caching for now.
-
Ambient.Impact →
committed ded69cc4 on 2.x
-
Ambient.Impact →
committed c41362db on 2.x
Upgraded Turbo to 8.0.0-beta.2: This contains a lot of bug fixes and...
-
Ambient.Impact →
committed c41362db on 2.x
- Status changed to Postponed
6 months ago 4:45pm 14 October 2024 - 🇨🇦Canada ambient.impact Toronto
Updating the issue title and summary to reflect to the current state of the implementation. I've had a chance to work on the issue fork, and it seems it mostly works now if we detach behaviours on the
turbo:before-cacheevent but there are still some remaining issues:turbo:before-cacheis not currently able to be delayed until a page has transitioned out, so if a behaviour detaching causes visible changes to the page, these will be briely seen before a transition out has begun; there are potential solutions to this:- TBD; coffee shop closing back later lolol
- The core Navigation is even more broken due to lacking detach callbacks for most of its JavaScript; this is fixable by adding detach callbacks, but will take some time and untangling of its spaghetti JavaScript; see 🌱 Turbo: Tracking issue of core and contrib behaviours that need fixes to correctly detach and then attach Active