Releases: hotwired/turbo
Releases · hotwired/turbo
v7.0.0-beta.5
- FIXED: The
<turbo-frame busy>attribute is now applied during frame form submissions. [#156] - FIXED:
<turbo-frame>elements with self-referentialsrcattributes now log an error to the console instead of reloading indefinitely. [#98, #165, #182] - FIXED: The
Turbo-Frameheader is now present on HTTP requests from form submissions parented by or targeting a<turbo-frame>element. [#86, #110, #166] - FIXED: The
<html data-turbo-preview>attribute is correctly applied during navigation again, and autofocus behavior has been restored. [#117, #159, #169] - FIXED: You can now add or remove the
<turbo-frame disabled>attribute at runtime to disable or re-enable a frame. [#181] - FIXED: Form submitter parameters will no longer be duplicated under certain circumstances in Safari. [#184]
- FIXED: Setting
srcon a<turbo-frame loading="lazy">element navigates the frame immediately if the frame has already been loaded before. [#212] - FIXED:
<turbo-frame src>elements no longer reload after reconnecting to the DOM [1d52b23] or after being cloned for the snapshot cache [dd0aaf8]. [#150, #204] - FIXED: Form submission failures now appear in the console. [#220]
- FIXED: Redirections from form submissions parented by or targeting a
<turbo-frame>element now update the frame'ssrcattribute with the final URL. [#223, #224] - FIXED: Turbo now preserves playback state of
<audio>and<video>elements withdata-turbo-permanentannotations during rendering. [#221, #222, #226] - FIXED: The
data-turbo="false"annotation for disabling Turbo Drive now works for form submissions parented by or targeting a<turbo-frame>element. [#227, #228] - FIXED: You can now set the
data-turbo-actionattribute on forms or form submitters to specify which visit action to use. [#231]
v7.0.0-beta.4
- NEW: Support for persistent
data-turbo-permanentelements during Turbo Frames navigation. [#64, #71] - NEW: Support for
<form enctype>and URL-encoded form submissions. [#76, #128] - CHANGED: Top-level
<form action="get">submissions now become Turbo Drive visits. That means they'll dispatch visit events liketurbo:before-visitandturbo:visit, but not theturbo:submit-startorturbo:submit-endevents. [#126, #127] - FIXED: Successive
<form action="get">submissions to the current location no longer accumulate redundant query parameters. [#107, #108] - FIXED: The Turbo Streams
Accept:header is only present for non-idempotent form submissions. [#52, #139] - INTERNAL: Development builds have moved to the new hotwired/dev-builds repository shared with Stimulus.
- INTERNAL: The
Locationclass has been replaced by the DOM URL API. [#90] - INTERNAL: The page and frame rendering systems have been unified, and rendering is now asynchronous. [#133]
v7.0.0-beta.3
- NEW: You can use
<turbo-frame loading="lazy" src="...">to defer loading the source URL until the frame appears in the viewport. [#53] - CHANGED: The Turbo Streams MIME type has changed from
text/html; turbo-streamtotext/vnd.turbo-stream.html. Server-side framework integrations will need to update accordingly. [#24, #91, #93] - CHANGED: Form submissions may now return empty HTTP 201 or 204 responses.
- CHANGED: Turbo empties the frame and logs an error to the console when a matching
<turbo-frame>is missing in the response. [#31] - FIXED: Turbo waits until the initial page load has completed before enabling manual scroll restoration to avoid losing the initial scroll offset on locations with anchors. [#63]
v7.0.0-beta.2
- CHANGED: Turbo now renders 4xx and 5xx HTML error responses to form submissions for both Turbo Drive and Turbo Frames. We suggest serving form validation errors with a HTTP 422 status. [#39]
- CHANGED: Turbo ignores form submissions where the form or triggering button has a
data-turbo="false"annotation. [#3] - CHANGED: Updated a handful of documentation links to point to the new Stimulus site. [#17, #27]
- INTERNAL: Set up CI and configured the test suite to run on Firefox. [#60]
v7.0.0-beta.1
Turbo 7.0.0-beta.1