fix(modal, popover): remove trigger click listeners when overlay is unmounted #26167
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
ionic-docs
repo, in a separate PR. See the contributing guide for details.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?
When
ion-modal
andion-popover
are disconnected from the DOM, the click listener for opening them viatrigger
is not removed. Because the listener is on the button etc. rather than the overlay, it isn't garbage collected either.Issue URL: resolves #26138
What is the new behavior?
For both modal and popover, trigger click listeners are removed and added as the overlay is unmounted and mounted in the DOM.
I added tests for the overlay still being openable after it's been removed and re-added, but there isn't currently a way to check click listeners currently on an element (at least not without monkey-patching
addEventListener
/removeEventListener
beforehand), so I wasn't able to add a test for that part. I manually verified the behavior in the dev tools, though.Does this introduce a breaking change?
Other information