Repository navigation
Conversation
The table height was only recalculated on splitter drag, so after a window resize it either left a gap above the agent tabs or ran under them. Use a ResizeObserver on the panes instead, keeping the old calculation as a fallback.
Deenyoro
force-pushed
the
fix/dashboard-pane-heights
branch
from
November 2, 2026 17:19
be48390 to
157453c
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.
The agent table height comes from the screen height and splitter position (
SET_SPLITTER). It's only recalculated when the splitter is dragged. If the window changes size after the dashboard loads, the table keeps its old height:The agent tabs (
tabHeight) have the same issue.This change uses a ResizeObserver on the two splitter panes to size the table and the tabs from the space they actually have. The old calculation is still used for the first paint and as a fallback. The tabs pane is also clamped when the window gets shorter, so the table doesn't get squeezed out.
Tested on develop vs this branch with 197 sample agents. The numbers are the gap between the bottom of the table and the bottom of its pane:
Before / after (window resized to portrait after loading, sample data):