Add 'data-turbo' => 'false' in markdown link to escape turbo-frames#1136
Conversation
|
@unasuke Nice find on the root cause — links inside the rating widget's turbo-frame really were broken ("Content missing"), and One concern about the chosen attribute, though:
Since this app sets MarkdownRenderer.new(filter_html: true, hard_wrap: true, link_attributes: {'data-turbo' => 'false'})Frame link-interception respects |
Yes. And I'd been thinking this was acceptable. Indeed, I had overlooked the side effects for anchor links and autolinked emails. I'll go ahead and adopt the proposed correction. |
Links inside internal comments live within the rating widget's turbo-frame, so clicking a comment URL triggered a frame navigation whose response lacked that frame, rendering "Content missing". Since Turbo Drive is disabled app-wide, links are only ever intercepted when inside a turbo-frame. Marking rendered links data-turbo="false" makes those frame-internal links navigate natively in the same tab (fixing the bug) while being a no-op everywhere else -- no new-tab side effects on other markdown surfaces (public guidelines, anchor links, autolinked emails, mail preview) and no tabnabbing surface to mitigate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2c96025 to
33d51c1
Compare
'data-turbo' => 'false' in markdown link to escape turbo-frames
|
@amatsuda Applied 2026-07-11.212215.mp4 |
|
@unasuke Thank you! |
What
Links inside internal comments live within the rating widget's turbo-frame, so clicking a comment URL triggered a frame navigation whose response lacked that frame, rendering "Content missing".
Screenshots
before
2026-07-11.175226.mp4
after
2026-07-11.175143.mp4
ref