src/ui/tabs/order_in_progress_tab.rs (2)

335-350: Footer height heuristic looks reasonable, but worth noting the chat area can collapse to 0.

footer_height is chosen from spare_below_header_input (= main_area.height − header_height − input_height). When that spare is exactly 3 and the 3-line footer is selected, the Min(0) chat constraint at Line 356 collapses to 0 rows and the chat becomes invisible (only header + input + footer remain). On very small terminals this is probably acceptable, but you may want to bias toward leaving at least 1 row for chat — e.g. require spare_below_header_input >= 4 for the 3-line footer and >= 3 for the 2-line footer.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/ui/tabs/order_in_progress_tab.rs` around lines 335 - 350, The
footer_height selection can consume the last available chat row when
spare_below_header_input equals the footer size; update the heuristic in the
block that computes spare_below_header_input/footer_height (variables:
spare_below_header_input, footer_height, main_area, header_height, input_height)
to bias leaving at least one chat row by raising thresholds — e.g. require
spare_below_header_input >= 4 to pick a 3-line footer and >= 3 to pick a 2-line
footer (so the chat's Min(0) constraint does not collapse the chat to 0 height).

---

424-534: Footer refactor LGTM.

Collapsing the per-line Paragraphs into a single Paragraph::new(footer_text).wrap(Wrap { trim: true }) over the full footer rect correctly addresses the “wrapped hints have nowhere to go” problem described in the PR objectives. The 3/2/1-line content variants are consistent across the input-enabled / disabled branches and use the same separator style.

One small nit: in the 3-line input-enabled variant (Lines 439-442), middle line only contains SHIFT_C | SHIFT_F while the surrounding lines pack four hints each — feels a bit lopsided. Consider rebalancing (e.g. moving SHIFT_R_RELEASE or SHIFT_V_RATE up to line 2) for visual symmetry. Non-blocking.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/ui/tabs/order_in_progress_tab.rs` around lines 424 - 534, The 3-line
footer variant when app.order_chat_input_enabled (in the footer_height >= 3
branch) has an unbalanced middle line containing only
FOOTER_MYTRADES_SHIFT_C_CANCEL and FOOTER_MYTRADES_SHIFT_F_FIAT_SENT; move one
of FOOTER_MYTRADES_SHIFT_R_RELEASE or FOOTER_MYTRADES_SHIFT_V_RATE from the
third line up into that middle Line (the block that constructs Text::from(vec![
Line::from(format!(...)), Line::from(format!(...)), Line::from(format!(...)) ])
under the app.order_chat_input_enabled branch) so the three lines are more
visually balanced while keeping the same separators and overall content.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes