Terminate async JS handlers when DOM owner is destroyed #2244
Conversation
This file contains 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
mvorisek
force-pushed
the
view_unload
branch
2 times, most recently
from
c744b0e to
0702fcf
Compare
mvorisek
changed the title
mvorisek
force-pushed
the
view_unload
branch
6 times, most recently
from
bc27df9 to
d2c8800
Compare
mvorisek
changed the title
mvorisek
force-pushed
the
view_unload
branch
3 times, most recently
from
aaab7d4 to
5143d3c
Compare
mvorisek
changed the title
mvorisek
changed the title
Closed
mvorisek
force-pushed
the
view_unload
branch
4 times, most recently
from
c8ae061 to
8378c91
Compare
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.
fix #393
All DOM element related async callbacks must be terminated/removed before the element is removed/replaced.