Turbolinks: clean up injected scripts and styles on page navigation #3283
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Closes #3128
This updates the turbolinks integration to remove any client hydration scripts before page navigation.
By default turbolinks will leave
<head>
scripts in place during page navigation, by manually removing them we leave it up to turbolinks to add them back if needed, triggering a fresh script execution in the browser and re-hydrating the components again 🥳styles
Injected style bundles are also cleaned up on navigation now - after each page navigation they're moved down into the body where Turbolinks will clean them up when diffing the new page
Testing
Tested locally with the reproduction from #3128
Docs
None, bugfix only
Note
Why two different methods for cleaning up scripts vs styles? Because it actually works...🤣 If scripts are moved into the body after page navigation it breaks the hydration process. If styles are removed from the head they're never actually replaced with the new page's link (not sure why, some quirk in Turbolinks diffing 🤷)