This repository was archived by the owner on Feb 25, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6k
FlutterFragment predictive back #52302
Merged
justinmc
merged 12 commits into
flutter:main
from
justinmc:flutter-fragment-predictive-back
May 28, 2024
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
89629fb
Seems to work whether Flutter is the first acitivty or not
justinmc bf4e1ec
Work with original onBackPressed mechanics
justinmc c396216
Merge branch 'main' into flutter-fragment-predictive-back
justinmc 1ae637d
Fix from math1man review https://github.com/flutter/engine/pull/44865…
justinmc 7cd3383
popSystemNavigator should restore onBackPressedCallback to original s…
justinmc 3733332
Test that popSystemNavigator preserves enabled state
justinmc 0d95e27
An attempt at testing the callback being enabled/disabled, but not wo…
justinmc 6d69cfc
Merge branch 'main' into flutter-fragment-predictive-back
justinmc c06300a
Fix flipped logic, and add comments explaining what's going on
justinmc 48765ee
Merge branch 'main' into flutter-fragment-predictive-back
justinmc c785e98
Clarify comment
justinmc 1ff7c32
Whoops, should have gotten this in the merge commit
justinmc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Merge branch 'main' into flutter-fragment-predictive-back
- Loading branch information
commit 48765ee16c46679552e921fca8cd2be9118a3209
There are no files selected for viewing
This file contains hidden or 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
You are viewing a condensed version of this merge commit. You can view the full changes here.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reading this test shouldn't the back pressed be handled by the framework because of the code on 306?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comment above should help explain this a bit. shouldAutomaticallyHandleOnBackPressed enables predictive back, while setFrameworkHandlesBack determines whether Android or the framework handle the back gesture.