Skip to content

fix(site): add padding below thinking-only assistant messages - #24140

Merged
jaaydenh merged 2 commits into
mainfrom
fix/thinking-only-message-padding
Apr 9, 2026
Merged

jaaydenh merged 2 commits into
mainfrom
fix/thinking-only-message-padding

Conversation

@jaaydenh

@jaaydenh jaaydenh commented Apr 8, 2026 •

Copy link
Copy Markdown
Contributor

closes CODAGT-122

Add a spacer div that renders only when an assistant message lacks the action bar, matching the height the action bar would provide.

🤖 Generated by Coder Agents

@github-actions github-actions Bot added the community Pull Requests and issues created by the community. label Apr 8, 2026
@jakehwll jakehwll removed the community Pull Requests and issues created by the community. label Apr 8, 2026
@jaaydenh
jaaydenh force-pushed the fix/thinking-only-message-padding branch from 32ed5fb to 4156670 Compare April 9, 2026 05:38
@jaaydenh
jaaydenh requested a review from DanielleMaywood April 9, 2026 05:51
@jaaydenh
jaaydenh marked this pull request as ready for review April 9, 2026 06:02
Reasoning content populates parsed.reasoning but not parsed.markdown,
so hasCopyableContent evaluates to false and the action bar is not
rendered. The action bar provides ~24px of invisible layout space
below each message; without it, thinking-only assistant messages sit
flush against the next user bubble.

Add a spacer div that renders only when an assistant message lacks
the action bar, matching the height the action bar would provide.
@jaaydenh
jaaydenh force-pushed the fix/thinking-only-message-padding branch from 1ba1505 to 2d16c5f Compare April 9, 2026 06:07
@jaaydenh
jaaydenh merged commit f957981 into main Apr 9, 2026
27 checks passed
@jaaydenh
jaaydenh deleted the fix/thinking-only-message-padding branch April 9, 2026 09:17
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants