ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #turbo
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
Goal Determine whether a Turbo Streams WebSocket connection remains open or automatically reconnects when the server detects that a user’s authentication has expired or been revoked. Constraints Least‑privilege enforcement relies on server‑side middleware; the stream endpoint must reject messages from unauthenticated or unauthorized users. When a session tok
Determine whether Turbo Drive automatically discards or updates its internal turbo-cache when a navigation is interrupted because the server returns malformed HTML or a mismatched checksum. The behavior is not documented; observations suggest stale cache entries may persist, potentially causing incorrect DOM updates on subsequent navigation attempts, especia
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
Cache key stability across deployment environments Turborepo v2 defaults to strict environment variable mode, where only variables declared in globalEnv or a task's env array participate in the task hash. Framework-prefixed variables such as NEXT_PUBLIC_* or VITE_* are inlined at build time, so their values must vary the cache key when the target environment
Developers using Turbo Drive often need to limit how long a page visit can wait for a server response, especially when dealing with unreliable backends or long‑running endpoints. The current implementation relies on the Fetch API and provides no default timeout; a visit proceeds until the network layer signals failure or the server replies. To impose a limit
Goal: Ensure that date/time fragments rendered by Rails view helpers display the correct offset after a Turbo Stream update when a user changes their preferred time zone. Constraint: Turbo Streams inserts server‑generated HTML without performing any additional client‑side time‑zone conversion, and its cache‑busting flags do not automatically invalidate cache
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
Goal We want to deliver a large dataset to the browser in paginated chunks using Turbo Streams while keeping the server‑side query bounded by limit/offset or cursor logic. Constraints Turbo only renders the HTML fragment; it does not enforce database limits. Pagination helpers such as paginate set limit and offset , but those values must be propagated throug
rails