Increase z-index of SfxPopper instead of its children #1655
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
Contributor
Author
|
/backport to stable26 |
Contributor
Author
|
/backport to stable25 |
backportbot-nextcloud
bot
added
the
backport-request
skjnldsv
approved these changes
May 12, 2023
Signed-off-by: Louis Chemineau <[email protected]>
artonge
force-pushed
the
artonge/fix/sub_popper_use
branch
from
5f0acbf to
9648987
Compare
This was referenced May 12, 2023
backportbot-nextcloud
bot
removed
the
backport-request
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.
Each popper should have its own
z-index, so setting the samez-indexto all poppers prevent accessing sub-poppers.Here we increase the
z-indexof all poppers container to not mess with their individualz-index.Fix nextcloud/photos#1683