Skip to content

fix(site): hide bottom spacer on last session thread#24248

Merged
jeremyruppel merged 2 commits intomainfrom
jeremyruppel/sessions-page-spacer
Apr 14, 2026
Merged

fix(site): hide bottom spacer on last session thread#24248
jeremyruppel merged 2 commits intomainfrom
jeremyruppel/sessions-page-spacer

Conversation

@jeremyruppel
Copy link
Copy Markdown
Contributor

If theres is no agentic loop on the last thread, there will be a space between the bottom of the section and the session completed lines. This fixes that

Before
Screenshot 2026-04-10 at 12 25 39 PM

After
Screenshot 2026-04-10 at 12 26 13 PM

If theres is no agentic loop on the last thread, there will be a space between the bottom of the section and the session completed lines. This fixes that
@github-actions github-actions Bot added the community Pull Requests and issues created by the community. label Apr 10, 2026
@jeremyruppel jeremyruppel changed the title fix(site): hide bottom spacer on last thread fix(site): hide bottom spacer on last session thread Apr 10, 2026
@jeremyruppel jeremyruppel removed the community Pull Requests and issues created by the community. label Apr 10, 2026
@jeremyruppel jeremyruppel requested a review from aslilac April 10, 2026 16:27
@jeremyruppel jeremyruppel requested a review from jakehwll April 10, 2026 16:28
Use a CSS selector to hide the bottom spacer on the last thread instead
of passing an isLastThread prop through the component tree. The threads
wrapper uses [&>.thread-gap:last-child]:hidden to target the spacer
only when it is the final element in the container.
@jeremyruppel jeremyruppel merged commit 4d4266a into main Apr 14, 2026
27 checks passed
@jeremyruppel jeremyruppel deleted the jeremyruppel/sessions-page-spacer branch April 14, 2026 13:48
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 14, 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