[Feature]: scrollable error toasts

[MahmoudHilani]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

currently, if an error toast is too long or if there are multiple toasts leading to page overflow, there is no way to see the overflowed text. (ignore the toast button, that's for testing)

Proposed solution

make the toasts scrollable without a scroll bar, keeping the same look just with more functionality. I have also accounted for the animations and hovers. I have developed the solution but I'm posting an issue so I get permission to send a PR.

Why this matters

I got a very long error when first trying t3 code and it was hard to get to understand what was needed to do. Hopefully this will help others.

Smallest useful scope

check when the dialogs are hovered and overflow the page, enable scrolling if so

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[juliusmarminge]

Long errors now belong in persistent diagnostics and work-log surfaces; making stacked transient toasts scrollable would preserve the wrong error UX and create another nested-scroll region. We are not taking this approach.

This was closed as part of a large repo-wide maintenance sweep. If you think it's still relevant, please reopen.