Skip to content

Add bottom padding below TUI footer/prompt (CODE-1878)#13850

Open
warp-dev-github-integration[bot] wants to merge 1 commit into
masterfrom
oz/tui-footer-bottom-padding-code-1878
Open

Add bottom padding below TUI footer/prompt (CODE-1878)#13850
warp-dev-github-integration[bot] wants to merge 1 commit into
masterfrom
oz/tui-footer-bottom-padding-code-1878

Conversation

@warp-dev-github-integration

Copy link
Copy Markdown
Contributor

Description

The headless TUI's terminal-session root container (TuiTerminalSessionView::render) had horizontal and top padding but no bottom padding, so the footer/prompt rendered flush against the bottom terminal edge. Commit 28f25535f8 ("Proper long running command rendering", #13774) added .with_padding_top(2) without a matching bottom pad.

This adds .with_padding_bottom(1) to the view root (extracted into a small wrap_view_root_padding helper so it's unit-testable), giving one blank row of whitespace below the footer/prompt — matching the Figma spec (frame 323:17499, ~12px ≈ 1 cell row of whitespace below the footer).

Linked Issue

Fixes CODE-1878https://linear.app/warpdotdev/issue/CODE-1878

Testing

  • Added a render-to-lines unit test (view_root_pads_a_blank_row_below_the_footer) asserting the trailing blank padding row below the footer.
  • cargo test -p warp_tui --lib → 277 passed. (cargo fmt + cargo clippy -p warp_tui --all-targets --tests -- -D warnings clean.)
  • Live verified with a logged-in warp-tui-dev build under tmux (120x40), per tui-verify-change. Before: footer on the last terminal row (row 40, flush). After: footer on row 39 with a blank padding row 40.

Screenshots / Videos

Captured tmux capture-pane frames (attached as a run artifact):

Before (footer flush to bottom edge):

 38  │                                                                                     │
 39  └─────────────────────────────────────────────────────────────────────────────────────┘
 40  ← for conversations                          auto (cost-efficient) /workspace/warp ↬ master • +72 -6

After (one blank padding row below the footer):

 38  └─────────────────────────────────────────────────────────────────────────────────────┘
 39  ← for conversations                          auto (cost-efficient) /workspace/warp ↬ master • +72 -6
 40

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-BUG-FIX: Fixed the headless TUI footer/prompt rendering flush against the bottom terminal edge with no padding.

Conversation: https://staging.warp.dev/conversation/7817fa6c-ef0d-4f52-b27a-08aeb9673dec
Run: https://oz.staging.warp.dev/runs/019f6ca8-67ba-7588-b055-70f5ba1ea4ed

This PR was generated with Oz.

The headless TUI's terminal-session root container had top/horizontal
padding but no bottom padding, so the footer/prompt rendered flush against
the bottom terminal edge. Commit 28f2553 added `.with_padding_top(2)`
without a matching bottom pad.

Wrap the view root with `.with_padding_bottom(1)` (extracted into a small
`wrap_view_root_padding` helper) so one blank row renders below the footer,
matching the Figma spec (~1 cell row of whitespace below the footer). Add a
render-to-lines unit test asserting the trailing blank padding row.

Fixes CODE-1878

CHANGELOG-BUG-FIX: Fixed the headless TUI footer/prompt rendering flush against the bottom terminal edge with no padding.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jul 16, 2026
@kevinyang372 kevinyang372 marked this pull request as ready for review July 16, 2026 22:46
assert_eq!(actual_update.new_size().columns(), 42);
}

fn render_lines_sized(

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need these test cases

.with_padding_x(2)
.with_padding_top(2)
.finish()
wrap_view_root_padding(terminal_content.finish()).finish()

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be inline?

@ianhodge

Copy link
Copy Markdown
Member

@oz-agent address these comments and fix CI

@ianhodge

Copy link
Copy Markdown
Member

@warp-agent are you the right one to trigger here

@oz-for-oss

oz-for-oss Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

@ianhodge

You can view the conversation on Warp.

Powered by Oz

@ianhodge

Copy link
Copy Markdown
Member

@warp-agent try again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants