Fix Dialog
unmounting problem due to incorrect transitioncancel
event in the Transition
component on Android
#2071
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.
This PR fixes an odd issue where the
transitioncancel
event was fired on Android devices and thetransitionend
event was never fired. Therefore theTransition
component was never "done", which in turn means that theDialog
never unmounted because the internalOpenClosed
state didn't change yet.Removing the
transitioncancel
event handling altogether fixes this issue. This ensure that it now works on Android and still works on Safari, Chrome, iOS Safari, ...The good part is that we didn't really do anything with the
transitioncancel
event anyway, we just removed all the active listeners.Fixes: #2032