ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #turbo
Module execution state not preserved across Turbo Drive visits Turbo Drive replaces the <body> while keeping the <head> intact during navigation, but <script type="module"> elements in the new page cause their modules to re-evaluate on every visit. This behavior can duplicate initialization side effects — such as event listener registration
Turbostream Targeting Error Inside Nested Turbo Frames The goal is to determine whether a Turbo Stream action that references an element inside an inner Turbo Frame actually updates that inner frame’s content or instead applies to the outer frame’s DOM. The current Turbo specification lists selector resolution but omits a clear rule for nested frames, and di
Unresolved behavior The current Turbo Streams implementation in Rails 7.2 silently ignores actions whose target attribute does not match an element in the client DOM. No error is thrown, and the page remains unchanged. Developers face a design decision: continue relying on this silent‑ignore semantics or implement a new configuration that raises an error or
Goal Determine whether a Turbo Drive form write was processed when the server returns a Turbo Stream that targets a DOM ID missing from the page, and whether the client can safely offer a retry without duplicating a non-idempotent POST, PUT, or DELETE. Constraints Turbo Drive submits forms via fetch, does not automatically retry, and does not attach idempote
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 Determine the best approach for users on bandwidth‑limited connections while preserving site functionality and security. Constraints Opera Turbo compresses traffic via Opera’s servers, potentially lowering image resolution and altering exact byte streams. Native image‑optimization (lazy‑loading, WebP conversion) is a built‑in feature that maintains imag
Hibernate Query.setTimeout() establishes a JDBC statement timeout, but the framework does not guarantee cancellation of the underlying query when the timeout expires. This behavior creates ambiguity for applications that rely on timely query termination, especially when pagination via setMaxResults and setFirstResult is involved. The timeout applies at the s
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
opera