Add panel section context for orientation-aware layouts #7724
+159
−99
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
manzt
force-pushed
the
manzt/orientation-context
branch
from
a892dcd to
6ac377d
Compare
mscolnick
approved these changes
Jan 7, 2026
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.
With #7697, panels can render in two locations: the sidebar (narrow, vertical) or the developer panel (wide, horizontal). Components within panels (may) need to know their context to adapt their layout accordingly.
These changes introduce a
PanelSectionContextthat provides "sidebar" or "developer-panel" to child components, along with ausePanelOrientationhook that maps section to the appropriate layout direction. The scratchpad uses this mechanism to switch between vertical and horizontal panel arrangements depending on where it's rendered.I think the other panels should be fine, but this should give us a good foundation of improving other panels if requested in the future.
Screen.Recording.2026-01-07.at.2.59.31.PM.mov