Skip to content

fix: info panel opens under sidebar instead of into content area#312

Merged
PureWeen merged 1 commit intomainfrom
fix/if-i-click-the-i-next-to-the-session-nam-20260308-1557
Mar 8, 2026
Merged

fix: info panel opens under sidebar instead of into content area#312
PureWeen merged 1 commit intomainfrom
fix/if-i-click-the-i-next-to-the-session-nam-20260308-1557

Conversation

@StephaneDelcroix
Copy link
Copy Markdown
Collaborator

Problem

Clicking the ℹ︎ button next to the session name in the expanded view caused the info panel to partially open under the left sidebar pane.

Root Cause

The .info-panel in ExpandedSessionView.razor.css used right: -0.5rem positioning, which made the dropdown extend leftward from the trigger. When the trigger was near the left edge of the content area (right after the sidebar), the panel extended past the content boundary and was clipped by overflow: hidden on .expanded-card, making it appear to open under the sidebar.

Fix

Changed right: -0.5remleft: 0 so the panel extends rightward into the content area. This matches the existing pattern used by the sidebar header's info panel in SessionSidebar.razor.css.

Testing

  • 5 new regression tests in InfoPanelPositionTests.cs verify the panel uses left-anchored positioning
  • All 2110 tests pass
  • Mac Catalyst build succeeds

The ExpandedSessionView info panel (ℹ︎ next to session name) used
`right: -0.5rem` positioning, which made the dropdown extend leftward.
When the trigger was near the left edge of the content area, the panel
extended past the content boundary and was clipped by overflow:hidden
on the parent, appearing to open partially under the sidebar.

Changed to `left: 0` so the panel extends rightward into the content
area, matching the sidebar header info panel's positioning pattern.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@PureWeen PureWeen merged commit ac81918 into main Mar 8, 2026
@PureWeen PureWeen deleted the fix/if-i-click-the-i-next-to-the-session-nam-20260308-1557 branch March 8, 2026 22:19
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