Repository navigation
Conversation
Contributor
|
@HardMax71 is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
break-words(overflow-wrap: break-word) toMessageResponseandReasoningContent. A word that doesn't fit on a line now breaks inside the message; text that fits is unchanged.QueueandTerminalalready usebreak-words.I chose it over
wrap-anywherebecauseanywherealso lowers the min-content width, which changes how tables are sized: in the same check, a 7-column table shrank from 617 px to 588 px, and narrow columns would break words mid-word instead of scrolling. Withbreak-wordsthe table stays at 617 px and scrolls as before. Code blocks scroll either way.The test setup doesn't load Tailwind CSS, so the two new tests in
message.test.tsxandreasoning.test.tsxcheck that the class is there; both fail on main and pass here. To check the layout, I compiled the Tailwind 4.1.18 CSS for the package and rendered the repro from the issue in Chromium: inline code that ran 850 px (assistant), 866 px (user) and 832 px (reasoning) past the edge now ends inside it. The full@repo/elementssuite passes (960 tests). No docs change, since props and usage stay the same.Closes #515