-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(overlays): getTop now returns the top-most presented overlay #24547
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is off to a great start 🚀 ! The angular test comment is not blocking, though it seems like we could simplify that by making it a test in core rather than angular.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job! One idea for the commit subject could be fix(overlays): getTop now returns the top-most presented overlay
or something like that. getOverlay return visible overlay
likely does not mean much to a dev since getOverlay
is internal.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build
) was run locally and any changes were pushednpm run lint
) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the current behavior?
The logic for
getTop
does not take into consideration hidden overlays. With usages of an inline modal within a modal instance using a controller; you are unable to dismiss the modal usingdismiss
orgetTop
without an id.Issue Number: #19111, #24545
What is the new behavior?
Only visible overlays are returned in
getOverlay
, used by thegetTop
logic.Does this introduce a breaking change?
Other information
Reproduction app: https://github.com/sean-perkins/gh-24545-modal-top