- 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]