You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OverlayRoute.didPop shouldn't remove the overlays #370
Or at least, we should provide a way for that to be delayed. Right now, didPop() on _BottomSheetRoute delays its super.didPop() call, which is a contract violation.
TransitionRoute does this too, but even worse (didPop doesn't call super.didPop, then a completely unrelated _handleStatusChanged method calls super.didPop).
I found the didPop() linkages in TransitionRoute difficult to follow and I definitely didn't improve matters in _BottomSheetRoute().
Some of the tension comes from tests that want to call Navigator.pop() and then verify that their route is indeed gone. Similarly, the tests want to verify that showFoo().then( ) has removed whatever was being shown.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Hixie commentedon Nov 13, 2015
TransitionRoute does this too, but even worse (didPop doesn't call super.didPop, then a completely unrelated _handleStatusChanged method calls super.didPop).
HansMuller commentedon Nov 16, 2015
I found the didPop() linkages in TransitionRoute difficult to follow and I definitely didn't improve matters in _BottomSheetRoute().
Some of the tension comes from tests that want to call Navigator.pop() and then verify that their route is indeed gone. Similarly, the tests want to verify that showFoo().then( ) has removed whatever was being shown.
github-actions commentedon Sep 7, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.