Disable Turbolinks
See original GitHub issueDescription
Adding a simple data-turbo=false
attribute to <body>
on GitHub will make navigations use normal page loading instead of client-side transitions powered by GitHub’s “turbolinks”
For most users, the differences is likely negligible, that is until they are on a poor connection (airport/train/etc) where it will now be noticeably faster to open links in new tabs than let turbolinks do its thing.
Also see: https://jakearchibald.com/2016/fun-hacks-faster-content/
Screenshot
https://user-images.githubusercontent.com/952783/179869111-c90a81c6-1f3e-4fb5-9fe9-28e16e32f2e9.mov
Example URLs
https://github.com (every page)
Issue Analytics
- State:
- Created a year ago
- Reactions:74
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Rails: How to disable turbolinks in Rails 5? - Stack Overflow
Run yarn remove turbolinks · Delete this line from application pack file app/javascript/packs/application.js : require("turbolinks").start().
Read more >Disabling Turbolinks on a particular page · Issue #191 - GitHub
I'm wondering if there's way to disable Turbolinks on a particular page? I know one can disable Turbolinks via the incoming link, ...
Read more >Ruby on Rails Tutorial => Disable turbolinks on specific links
It is very easy to disable turbolinks on specific links. According to the official turbolinks documentation: Turbolinks can be disabled on a per-link...
Read more >Working with JavaScript in Rails - Ruby on Rails Guides
If you want to disable Turbolinks for certain links, add a data-turbolinks="false" attribute to the tag: < a href = "..." data ...
Read more >disable turbolinks on specific links in ruby on rails - Wikitechy
Turbolinks can be disabled on a per-link basis by annotating a link or any of its ancestors with data-turbolinks="false". Examples: // disables turbolinks...
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 Free
Top 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
Thank you for opening an issue, I would assume that that’s not the case for everyone and that there must be a reason to use ajaxed loads if GitHub invested so much on it over the years.
While this change would be beneficial to Refined GitHub (ajax causes a myriad of issues) this can’t be part of Refined GitHub.
I tried it. Turbo feels faster and less janky. What you’re experiencing in that tweet isn’t normal, the request is failing.
Native
https://user-images.githubusercontent.com/1402241/179943354-f1065a38-e1fb-4a0b-88d9-05a69c6277b0.mov
Turbo
https://user-images.githubusercontent.com/1402241/179943378-84595870-06ac-48cf-aca6-93c3b75f592f.mov
My connection (public wifi) is above average and the native version still doesn’t feel as fast as turbo’s
For good measure I also tried via hotspot. The speed is comparable, except that the native version has white flashes.
Native on mobile
https://user-images.githubusercontent.com/1402241/179945409-17e997c0-d7f7-433f-8011-e098ab893efa.mov
Turbo on mobile
https://user-images.githubusercontent.com/1402241/179945365-8f2081f5-b2d5-4620-ae17-cf383a9b21f2.mov