Closed edda closed 3 weeks ago
Latest commit: 7bf8b8c577ee60c7672a84033e5a4289892df499
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
PR Preview Action v1.4.8 :---: Preview removed because the pull request was closed. 2024-11-04 09:43 UTC
all look good
We could also define a property in the AppShellProvider and other components like AppShell to set the starting z-index. For example, we could specify startZIndex={60}. This would allow us to handle the z-index as usual (e.g., starting from 1 as in your last fix) while covering the Elektra case by setting the starting z-index higher than 50, such as 60.
We could also define a property in the AppShellProvider and other components like AppShell to set the starting z-index. For example, we could specify startZIndex={60}. This would allow us to handle the z-index as usual (e.g., starting from 1 as in your last fix) while covering the Elektra case by setting the starting z-index higher than 50, such as 60.
I like this idea. But it needs some more thought how exactly we want to do it. I'll add it to our collection epic for future improvements 🙏
Summary
This PR tries to improve upon the previous fix for the z-index stacking problem introduced in the recent refactoring of
PortalProvider
. While the previous fix in https://github.com/cloudoperators/juno/pull/565 solved the issue for Juno apps we still had potential z-index stacking issues if a Juno app was embedded into a host app with its own z-index stack. This is because the solution from the previous PR aimed to standardize all z-index on the root level to1
and then added stacks above this in the portaled components as necessary.In the cases where a Juno app is embedded in a host app with z-indexes higher than
1
the whole thing would break.This PR aims to fix this by setting a very high z-index (
9999
) for the portal root div which acts as the wrapper for all portals. So as long as the host app's z-index is at max9999
the z-stacking will be correct.Changes Made
z-index: 9999
to portal root div inPortalProvider
z-index
change toPageHeader
andLabel
from PR#565 since the new portal rootz-index
ensure proper stacking above these components for portaled componentsRelated Issues
Testing Instructions
Checklist