Repository navigation
fix(ui): prevent reasoning block from expanding chat playground layout #32485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
2 commits merged into
litellm_internal_staging
from
litellm_fix_reasoning_block_ui_overflow
Jul 9, 2026
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
32 changes: 32 additions & 0 deletions
32
ui/litellm-dashboard/src/components/chat_ui/ReasoningContent.test.tsx
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| import { render, screen, fireEvent } from "@testing-library/react"; | ||
| import { describe, it, expect } from "vitest"; | ||
| import ReasoningContent from "./ReasoningContent"; | ||
|
|
||
| describe("ReasoningContent", () => { | ||
| it("should render nothing when reasoningContent is empty", () => { | ||
| const { container } = render(<ReasoningContent reasoningContent="" />); | ||
| expect(container).toBeEmptyDOMElement(); | ||
| }); | ||
|
|
||
| it("should show reasoning content expanded by default and toggle on click", () => { | ||
| render(<ReasoningContent reasoningContent="thinking hard" />); | ||
|
|
||
| expect(screen.getByText("thinking hard")).toBeInTheDocument(); | ||
| expect(screen.getByText("Hide reasoning")).toBeInTheDocument(); | ||
|
|
||
| fireEvent.click(screen.getByRole("button")); | ||
|
|
||
| expect(screen.queryByText("thinking hard")).not.toBeInTheDocument(); | ||
| expect(screen.getByText("Show reasoning")).toBeInTheDocument(); | ||
| }); | ||
|
|
||
| it("should constrain width and break long words so it cannot expand the layout (regression #32481)", () => { | ||
| const longToken = "a".repeat(500); | ||
| render(<ReasoningContent reasoningContent={longToken} />); | ||
|
|
||
| const contentBox = screen.getByText(longToken).closest("div.mt-2"); | ||
| expect(contentBox).not.toBeNull(); | ||
| expect(contentBox).toHaveClass("max-w-full"); | ||
| expect(contentBox).toHaveStyle({ wordBreak: "break-word", overflowWrap: "break-word" }); | ||
| }); | ||
| }); |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wrap-break-wordis not a valid Tailwind CSS utility class and will be silently ignored by the browser. The correct Tailwind class foroverflow-wrap: break-wordisbreak-words. The actual break-word behavior here is covered by the inlinestyleprop, so this is harmless but dead/misleading code.