[12.x] Render newlines in query tooltip

[faisuc]

This fixes frontend breakage on the exception renderer by escaping tooltip content and converting newlines to <br>. It applies to queries, formatted source, request headers, and routing values, preventing layout overlap and syntax highlighter glitches when tooltip content contains newlines. Fixes #57246.

No breaking changes. This affects only the debug exception renderer UI and does not change any APIs.

[crynobone]

Fixed failling tests

[avosalmon]

This PR wouldn't fix #57246. The tooltip is not causing the issue, but text truncation is broken on syntax-highlighted queries. I opened a PR to fix text truncation. #57315

Having said that, I think it's still nice to render newlines in the tooltip.

[avosalmon]

I can't imagine $source contains newlines. The same goes for routing parameters and request headers.

[avosalmon]

Blade automatically escapes the variable.

Suggested change

	data-tippy-content="{!! nl2br(e($sql)) !!}"
	data-tippy-content="{{ nl2br($sql) }}"

[faisuc]

Thanks for the feedback!

For the query tooltip, the goal is to render actual line breaks inside the tooltip rather than escaped <br> tags. Using {{ nl2br($sql) }} would escape the <br> and show them as text, while nl2br(e($sql)) inside {!! !!} keeps it safe (escaped first) and still displays formatted newlines correctly.

Regarding the suggestion to switch to {{ nl2br($sql) }}, that would break the newline rendering because Blade would re-escape the <br> tags. I’m keeping nl2br(e($sql)) and outputting it as HTML so the SQL content is properly escaped before being rendered with <br>s:

data-tippy-content="{!! nl2br(e($sql)) !!}"

If you prefer avoiding raw braces, I can alternatively wrap it in an HtmlString so Blade won’t escape it again:

data-tippy-content="{{ new \Illuminate\Support\HtmlString(nl2br(e($sql))) }}"

I’ve updated the PR accordingly and kept this scoped only to queries, since other components like request headers or routing parameters are unlikely to contain newlines and don’t need the same handling.

Appreciate the clarification and review!

[avosalmon]

@faisuc With {{ nl2br($sql) }}, nl2br converts line breaks to <br> and then {{ }} escapes special characters, but Tippy.js supports HTML content.

framework/src/Illuminate/Foundation/resources/exceptions/renderer/scripts.js

Line 13 in 95fc3d0

allowHTML: true,

I tested this and confirmed that actual line breaks are rendered.

[faisuc]

PR updated