fix: resolve popover z-index stacking in settings cards #2465
+5
−3
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.
What does this PR do?
Fixes z-index stacking context issues where popover menus in settings cards get hidden behind subsequent cards.
Problem
Multiple
Card.Base
components with default styling create competing stacking contexts. When a popover opens in an upper card (like Git configuration or Global variables), it gets rendered behind lower cards in the DOM, making it partially or completely hidden.Solution
Added an optional
zIndex
prop to theCardGrid
component. This allows specific cards containing popover menus to establish proper stacking context without affecting all CardGrid instances.Changes Made
zIndex
prop toCardGrid
component (src/lib/components/cardGrid.svelte
)zIndex={10}
to Git configuration card inupdateInstallations.svelte
zIndex={10}
to Global variables card inupdateVariables.svelte
Test Plan
Local Testing Performed:
pnpm lint
andpnpm format
- all checks passedScreenshots
Git Configuration
Before Fix:

After Fix:

Global Variables
Before Fix:

After Fix:

Related PRs and Issues
Fixes #2464
Additional Notes
The
zIndex
prop is optional and defaults toundefined
, ensuring backward compatibility. Only cards that explicitly need elevated stacking (those with popovers) should use this prop. This is a non-breaking change.Have you read the Contributing Guidelines on issues?
Yes, I have read and followed the contributing guidelines.
Summary by CodeRabbit