Refactor back block handling in CommonScaffold to simplify dispose logic and improve readability #1650
+16
−15
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 issue #1620
This pull request refines how the system back button is handled in the app bar, especially distinguishing between edit and search modes. The main improvement ensures that the system back button is only blocked during edit mode, not search mode, leading to a more intuitive user experience.
Back button handling improvements:
_buildAppBarWrapinCommonScaffoldStateso thatSystemBackBlockis only applied during edit mode, allowing the system back button to function normally during search mode. (lib/widgets/scaffold.dart) [1] [2]disposemethod in_SystemBackBlockStateto immediately callunBackBlockbeforesuper.dispose(), ensuring proper cleanup without unnecessary post-frame callbacks. (lib/widgets/pop_scope.dart)