Skip to content

feat: v2 - runview tools window to become a panel#2523

Draft
maxy-shpfy wants to merge 1 commit into
masterfrom
07-14-feat_v2_-_runview_tools_window_to_become_a_panel
Draft

feat: v2 - runview tools window to become a panel#2523
maxy-shpfy wants to merge 1 commit into
masterfrom
07-14-feat_v2_-_runview_tools_window_to_become_a_panel

Conversation

@maxy-shpfy

@maxy-shpfy maxy-shpfy commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

Description

Introduces a "panel" variant for floating windows that renders chrome-less by default — the border, background, and shadow only appear on hover, and the header fades in on hover without shifting layout. When floating (not docked), a panel auto-fits its width to content rather than using a fixed size.

The Run Tools window is configured as a "panel" variant. When it is floating and undocked, RunToolsContent detects this via useOptionalWindowContext and switches from a vertical BlockStack layout to a horizontal InlineStack layout, so the action buttons render in a compact row instead of a column.

Related Issue and Pull requests

Type of Change

  • Bug fix
  • New feature
  • Improvement
  • Cleanup/Refactor
  • Breaking change
  • Documentation update

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Screenshots (if applicable)

Screen Recording 2026-07-14 at 1.42.24 PM.mov (uploaded via Graphite)

Test Instructions

  1. Open a run in the v2 Run View.
  2. Confirm the Run Tools window appears floating and undocked with no visible border, background, or header until you hover over it.
  3. Hover over the Run Tools window and confirm the border, background, shadow, and header fade in smoothly.
  4. Confirm the action buttons render in a horizontal row when the window is floating and undocked.
  5. Dock the Run Tools window to the left or right panel and confirm the buttons revert to the vertical column layout.
  6. Confirm dragging the window remains smooth with no layout shifts during the hover transition.

Additional Comments

The panel variant uses a dedicated group/panel Tailwind group (rather than group/window) to prevent the WindowHeader's window-hover purple tint from triggering on panel windows. Only color, border, and shadow properties transition — never position — so dragging performance is unaffected.

@github-actions

github-actions Bot commented Jul 14, 2026

Copy link
Copy Markdown

🎩 Preview

A preview build has been created at: 07-14-feat_v2_-_runview_tools_window_to_become_a_panel/fefd7e3

Copy link
Copy Markdown
Collaborator Author

@Mbeaulne Mbeaulne changed the base branch from 07-14-chore_v2_-_runview_run_menu_actions to graphite-base/2523 July 15, 2026 17:47
@Mbeaulne Mbeaulne force-pushed the 07-14-feat_v2_-_runview_tools_window_to_become_a_panel branch from c53483e to 208dffd Compare July 15, 2026 17:52
@Mbeaulne Mbeaulne force-pushed the graphite-base/2523 branch from a735cc1 to 54adeaf Compare July 15, 2026 17:52
@graphite-app graphite-app Bot changed the base branch from graphite-base/2523 to master July 15, 2026 17:53
@Mbeaulne Mbeaulne force-pushed the 07-14-feat_v2_-_runview_tools_window_to_become_a_panel branch from 208dffd to fefd7e3 Compare July 15, 2026 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants