I’m creating this topic in case anyone else bumps into a similar edge case with using
When turbo merges the HTML head, if any
noscript children are present, they will be processed.
I had an old login form that had a
noscript, css was used to set the
none for the normal content (the form).
With Turbo, on redirecting to the form after an incorrect login, the
The below tweets helped me understand what was going on. I agree that this is an edge case and seeing as Turbo encourages progressive enhancement, a fix is probably not needed.