This repository was archived by the owner on Sep 5, 2024. It is now read-only.
fix(dialog): remove focus trap focus listeners onRemove #12012
Merged
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.
PR Checklist
Please check that your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
In
MdDialogProvider.onRemove()
, we currently callremoveChild()
on thetopFocusTrap
andbottomFocusTrap
for the dialog and we let the browser handle GC'ing those detached Nodes. But we don't remove the'focus'
event listeners for each of these Nodes.Issue Number:
Relates to #11207. Closes #12010.
What is the new behavior?
focus
event listeners inMdDialogProvider.onRemove()
isNodeOneOf()
and ensure it returns aboolean
package-lock.json
Does this PR introduce a breaking change?
Other information
This doesn't seem to have a noticeable impact on the overall number of listeners when profiling.
Before
After