Conversation
aleclarson
added a commit
to goddard-ai/goddard
that referenced
this pull request
Sep 15, 2026
Completes the fix cherry-picked from egoist/waku#193, which covered only the preparing and send variants of the 26px composer buttons. The stop and queue-follow-up circles inside working-actions had the same squash, and the running-turn row is the tightest case.
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
1 participant
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.
Problem
When the window is narrow enough, the composer's fixed-size round buttons
(send, queue follow-up) get squashed by the flex layout, deforming
from circles into ellipses.
Solution
Add
flex_none()to the four fixed-size buttons in the composer's bottomcontrol row, so the layout can never shrink them below their intended
26px size.
Checks
Known limitations
The row can still overflow the composer card's rounded edge at very narrow
widths; a separate fix for that overflow is planned and will be discussed
in a follow-up issue.