[Design] Improve drag-and-drop of Panels - #355
Merged
Merged
Conversation
danyaberezun
marked this pull request as ready for review
September 1, 2026 19:40
danyaberezun
requested review from
Olga Lavrichenko (OLavrik),
Rustam Sadykov (SBOne-Kenobi),
danyaberezun and
Rinat S (rsolmano)
as code owners
September 1, 2026 19:40
danyaberezun
approved these changes
Sep 1, 2026
Reveal every currently-valid docking destination the instant a movable tab is picked up (subtle Primary treatment), then emphasize the one under the pointer (strong Primary), so the flexible panel/tab layout teaches itself. Two states derived from the existing drag state + each site's already-computed validity — no second drag-state machine, semantic Primary tokens only. - Tab headers outline the whole valid group (not individual tabs). - Center split: compact per-direction edge hints on drag-start; the true resulting half fills on hover. - Bottom docking: the persistent "Show bottom panel" rail is removed — an empty/hidden bottom now renders no chrome and reserves no height; during a compatible drag a 24px Primary drop zone appears over the accepting span (keyboard Mod+Shift+J still restores). View-scoped only; the layout document model, sync, and persistence are unchanged. Updates the layout SPEC and the bottom-panel/layout e2e specs to match.
danyaberezun
force-pushed
the
enhance-drag-drop-discoverability
branch
from
September 1, 2026 20:02
5e1b67d to
2bd042b
Compare
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
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.
Draft — still needs refinement. One known issue is that Terminal can currently only be opened by dragging it out of the bottom panel; when the bottom panel is absent, there is no other way to open Terminal yet.
This PR explores a more discoverable drag-and-drop model for the flexible panel layout. When a tab is picked up, available drop targets become visible. Hovering a target makes it more prominent and previews where the tab will be placed.
The goal is to make it clear that any tab can be moved to different areas of the layout without keeping the bottom panel permanently visible. When the bottom area is empty, it disappears completely and only appears as a drop target while dragging.
The interaction and drop-zone behavior follow the current Figma exploration and still need some visual/behavioral tuning before this is ready to merge.
Demo
Screenshots