-
Notifications
You must be signed in to change notification settings - Fork 6k
FlutterFragment predictive back #52302
Changes from 9 commits
89629fb
bf4e1ec
c396216
1ae637d
7cd3383
3733332
0d95e27
6d69cfc
c06300a
48765ee
c785e98
1ff7c32
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1056,6 +1056,11 @@ public void onAttach(@NonNull Context context) { | |
| delegate.onAttach(context); | ||
| if (getArguments().getBoolean(ARG_SHOULD_AUTOMATICALLY_HANDLE_ON_BACK_PRESSED, false)) { | ||
| requireActivity().getOnBackPressedDispatcher().addCallback(this, onBackPressedCallback); | ||
| // By default, Android handles backs, and predictive back is enabled. This | ||
| // can be changed by calling setFrameworkHandlesBack. For example, the | ||
| // framework will call this automatically in a typical app when it has | ||
| // routes to pop. | ||
| onBackPressedCallback.setEnabled(false); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You probably also need to update the implementation of
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @math1man Thanks for jumping back in here, I've been trying to catch back up on your comments from the last PR. Pushing a fix for that now.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No worries. Honestly, I think besides this comment everything looks good. Happy to look into anything specific you might be concerned about though. |
||
| } | ||
| context.registerComponentCallbacks(this); | ||
| } | ||
|
|
@@ -1663,16 +1668,29 @@ public boolean popSystemNavigator() { | |
| // Unless we disable the callback, the dispatcher call will trigger it. This will then | ||
| // trigger the fragment's onBackPressed() implementation, which will call through to the | ||
| // dart side and likely call back through to this method, creating an infinite call loop. | ||
| onBackPressedCallback.setEnabled(false); | ||
| boolean enabledAtStart = onBackPressedCallback.isEnabled(); | ||
| if (enabledAtStart) { | ||
| onBackPressedCallback.setEnabled(false); | ||
| } | ||
| activity.getOnBackPressedDispatcher().onBackPressed(); | ||
| onBackPressedCallback.setEnabled(true); | ||
| if (enabledAtStart) { | ||
| onBackPressedCallback.setEnabled(true); | ||
| } | ||
| return true; | ||
| } | ||
| } | ||
| // Hook for subclass. No-op if returns false. | ||
| return false; | ||
| } | ||
|
|
||
| @Override | ||
| public void setFrameworkHandlesBack(boolean frameworkHandlesBack) { | ||
| if (!getArguments().getBoolean(ARG_SHOULD_AUTOMATICALLY_HANDLE_ON_BACK_PRESSED, false)) { | ||
| return; | ||
| } | ||
| onBackPressedCallback.setEnabled(frameworkHandlesBack); | ||
| } | ||
|
|
||
| @VisibleForTesting | ||
| @NonNull | ||
| boolean shouldDelayFirstAndroidViewDraw() { | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -290,7 +290,7 @@ private FragmentActivity getMockFragmentActivity() { | |
| } | ||
|
|
||
| @Test | ||
| public void itDelegatesOnBackPressedAutomaticallyWhenEnabled() { | ||
| public void itDelegatesOnBackPressedWithSetFrameworkHandlesBack() { | ||
| // We need to mock FlutterJNI to avoid triggering native code. | ||
| FlutterJNI flutterJNI = mock(FlutterJNI.class); | ||
| when(flutterJNI.isAttached()).thenReturn(true); | ||
|
|
@@ -301,6 +301,8 @@ public void itDelegatesOnBackPressedAutomaticallyWhenEnabled() { | |
|
|
||
| FlutterFragment fragment = | ||
| FlutterFragment.withCachedEngine("my_cached_engine") | ||
| // This enables the use of onBackPressedCallback, which is what | ||
| // sends backs to the framework if setFrameworkHandlesBack is true. | ||
| .shouldAutomaticallyHandleOnBackPressed(true) | ||
| .build(); | ||
| FragmentActivity activity = getMockFragmentActivity(); | ||
|
|
@@ -318,8 +320,15 @@ public void itDelegatesOnBackPressedAutomaticallyWhenEnabled() { | |
| TestDelegateFactory delegateFactory = new TestDelegateFactory(mockDelegate); | ||
| fragment.setDelegateFactory(delegateFactory); | ||
|
|
||
| // Calling onBackPressed now will still be handled by Android (the default), | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. |
||
| // until setFrameworkHandlesBack is set to true. | ||
| activity.onBackPressed(); | ||
| verify(mockDelegate, times(0)).onBackPressed(); | ||
|
|
||
| // Setting setFrameworkHandlesBack to true means the delegate will receive | ||
| // the back and Android won't handle it. | ||
| fragment.setFrameworkHandlesBack(true); | ||
| activity.onBackPressed(); | ||
| verify(mockDelegate, times(1)).onBackPressed(); | ||
| } | ||
|
|
||
|
|
@@ -361,10 +370,20 @@ public void handleOnBackPressed() { | |
| TestDelegateFactory delegateFactory = new TestDelegateFactory(mockDelegate); | ||
| fragment.setDelegateFactory(delegateFactory); | ||
|
|
||
| assertTrue(callback.isEnabled()); | ||
|
|
||
| assertTrue(fragment.popSystemNavigator()); | ||
|
|
||
| verify(mockDelegate, never()).onBackPressed(); | ||
| assertTrue(onBackPressedCalled.get()); | ||
| assertTrue(callback.isEnabled()); | ||
|
|
||
| callback.setEnabled(false); | ||
| assertFalse(callback.isEnabled()); | ||
| assertTrue(fragment.popSystemNavigator()); | ||
|
|
||
| verify(mockDelegate, never()).onBackPressed(); | ||
| assertFalse(callback.isEnabled()); | ||
| } | ||
|
|
||
| @Test | ||
|
|
||
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.
I am still confused by this code. It looks like we are on a true branch of ARG_SHOULD_AUTOMATICALLY_HANDLE_ON_BACK_PRESSED.
Is this just saying that onBackPressedCallback.setEnabled should be the opposite of the argument passed to ARG_SHOULD_AUTOMATICALLY_HANDLE_ON_BACK_PRESSED?
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.
I'm going to push a commit to reword this comment to try to make it more clear.
ARG_SHOULD_AUTOMATICALLY_HANDLE_ON_BACK_PRESSED means that predictive back is enabled. onBackPressedCallback enabled means that Flutter is handling back gestures (typically because Flutter has Flutter routes to on its navigation stack). Disabled means that Android is handling back gestures, so it will either pop the Activity or go back to the phone's home screen.
So when the app starts, by default we let Android handle backs. If/when the Flutter app wants to change this, it calls setFrameworkHandlesBack and enables this callback.