Add option to deactivate Turbo Drive
See original GitHub issueCurrently, Turbo assumes that the whole framework is used from the point on it is imported. But as the whole Turbo Drive is immediately activated, this can break whole websites even though the developer might only use Turbo Frames.
We should either have an option to independently import the modules (#136) or for example, being able to deactivate Turbo Drive.
Sadly, <meta content="reload" name="turbo-visit-control">
is not enough as Turbo Drive still intercepts the native page loading and can still break things, for example, scrolling, as it scrolls to top while fetching the next page, which for example can cause an issue like wrong scroll positions with smooth-scroll CSS properties active.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Navigate with Turbo Drive - Hotwire Turbo
﹟ Disabling Turbo Drive on Specific Links or Forms. Turbo Drive can be disabled on a per-element basis by annotating the element or...
Read more >How can I disable Hotwire / Turbo (the Turbolinks replacement ...
UPDATE: comments in the videos have a different work around by setting turbo to 'false' and local to 'true' inside the form:
Read more >How to Enable or Disable Intel Turbo Boost Technology Max ...
How to Enable or Disable Intel Turbo Boost Technology Max Pop Up on Windows 10Intel Turbo Boost Technology or TBTM is a technology...
Read more >TurboWash - LG Top Load Washer | LG USA Support
To deactivate Turbo Wash from these cycles, select the Steam, Cold wash, or Fabric Softener options on your control panel.
Read more >Disable processor boost mode to prolong your battery life
How to disable Turbo Boost for AMD and Intel. ... Turbo Boost Switcher. The app adds a boost mode toggle button to the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@renestalder Yeah I didn’t word my last comment carefully enough: your issue is resolved in teh sense that if you put
data-turbo="false"
it will disable Turbo Drive, without affecting Frames/Streams. I was just pointing out that it would be nice to disable it from the JS backend rather than having to change each and every layout file in potentially large projects or projects where layouts are defined by customers and where you don’t want to break existing stuff.My PR would allow the JS backend to disable Drive by default, so the user would use
data-turbo="true"
to enable Drive on selected elements, making the behavior opt-in, rather than opt-out, just like how the rest of the framework operates.If you want to opt-out of Turbo Drive on all links and forms, you can add
data-turbo="false"
to any containing element. (The<html>
or<body>
elements should work.)https://turbo.hotwire.dev/handbook/drive#disabling-turbo-drive-on-specific-links-or-forms