feat: add internal API for nested overlays to bringToFront #8690
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.
Description
Part of #8521
Fixing the above issue where popover overlay ends up behind its parent dialog overlay requires us to add new APIs:
bringToFront()
recursively for all its nested overlays once its ownbringToFront()
is called),vaadin-popover
it should be basically the overlay where itstarget
is attached (note thatvaadin-popover
itself can be elsewhere).This PR focuses on the first part. I'm going to create a separate PR as a follow-up with the actual fix for popover.
Type of change