ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I'm designing navigation behavior for a Hotwire Turbo application where some endpoints can occasionally hang for a long time. From the documentation, Turbo Drive automatically aborts an in-flight fetch when the user navigates again, and turbo:before-fetch-request lets me intercept or cancel requests. What I cannot find is any documented, built-in network tim
Goal Allow applications to tune the exponential backoff schedule used when a Turbo Streams connection drops, so that reconnection aggressiveness can match infrastructure constraints such as load-balancer idle timeouts or upstream rate limits. Constraints and uncertainty Turbo 8.x implements a built-in reconnection loop with a starting delay near 500 ms and a
Hotwire apps on Turbo Drive 8.x (with turbo-rails 1.5+) keep a page snapshot cache keyed by URL and scroll position. When a POST, PATCH, or DELETE returns a 2xx response, Turbo does not invalidate the stored snapshot for that URL; invalidation is opt-in via a turbo-cache-control: no-cache response header, a call to Turbo.cache.clear() , or edits inside a tur
Limits of Turbo Frame fallback scroll restoration behavior The goal is to clarify whether Turbo should attempt to restore the previous scroll position when a Turbo Frame request returns HTML that lacks a matching frame element, causing a full‑page fallback. In Turbo 7.x the fallback performs a full‑page navigation that preserves the original request method a
The goal is to return the application to a consistent UI state after a Turbo Stream upgrade fails, preserving any unsaved form data while avoiding duplicate or stale Stream‑generated elements. Turbo Drive can be configured to either perform a full page reload or stay on the current page when a visit error occurs, but a full reload discards client‑side state
Turbo Drive caches GET responses to avoid full page reloads, but the framework does not automatically invalidate these caches when server-side data changes without corresponding cache-control directives. This can result in browser-reused stale HTML being presented during Turbo Drive navigation, even after a successful request. The interaction between Turbo’s
turbo