Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FlutterFragment predictive back #52302

Merged
merged 12 commits into from
May 28, 2024
Merged
Show file tree
Hide file tree
Changes from 11 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -1056,6 +1056,14 @@ 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);
// When Android handles a back gesture, it pops an Activity or goes back
// to the home screen. When Flutter handles a back gesture, it pops a
// route inside of the Flutter part of the app. By default, Android
// handles back gestures, so this callback is disabled. If, for example,
// the Flutter app has routes for which it wants to handle the back
// gesture, then it will enable this callback using
// setFrameworkHandlesBack.
onBackPressedCallback.setEnabled(false);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You probably also need to update the implementation of popSystemNavigator() to restore the previous state of the callback-enablement, instead of unconditionally re-enabling it on line 1673.

Copy link
Contributor Author

Choose a reason for hiding this comment

The 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.

Copy link
Contributor

Choose a reason for hiding this comment

The 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);
}
Expand Down Expand Up @@ -1663,16 +1671,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() {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -518,6 +518,7 @@ protected FlutterFragment createFlutterFragment() {
? TransparencyMode.opaque
: TransparencyMode.transparent;
final boolean shouldDelayFirstAndroidViewDraw = renderMode == RenderMode.surface;
final boolean shouldAutomaticallyHandleOnBackPressed = true;

if (getCachedEngineId() != null) {
Log.v(
Expand All @@ -542,6 +543,7 @@ protected FlutterFragment createFlutterFragment() {
.shouldAttachEngineToActivity(shouldAttachEngineToActivity())
.destroyEngineWithFragment(shouldDestroyEngineWithHost())
.shouldDelayFirstAndroidViewDraw(shouldDelayFirstAndroidViewDraw)
.shouldAutomaticallyHandleOnBackPressed(shouldAutomaticallyHandleOnBackPressed)
.build();
} else {
Log.v(
Expand Down Expand Up @@ -577,6 +579,7 @@ protected FlutterFragment createFlutterFragment() {
.transparencyMode(transparencyMode)
.shouldAttachEngineToActivity(shouldAttachEngineToActivity())
.shouldDelayFirstAndroidViewDraw(shouldDelayFirstAndroidViewDraw)
.shouldAutomaticallyHandleOnBackPressed(shouldAutomaticallyHandleOnBackPressed)
.build();
}

Expand All @@ -592,6 +595,7 @@ protected FlutterFragment createFlutterFragment() {
.transparencyMode(transparencyMode)
.shouldAttachEngineToActivity(shouldAttachEngineToActivity())
.shouldDelayFirstAndroidViewDraw(shouldDelayFirstAndroidViewDraw)
.shouldAutomaticallyHandleOnBackPressed(shouldAutomaticallyHandleOnBackPressed)
.build();
}
}
Expand All @@ -616,12 +620,6 @@ protected void onNewIntent(@NonNull Intent intent) {
super.onNewIntent(intent);
}

@Override
@SuppressWarnings("MissingSuperCall")
public void onBackPressed() {
flutterFragment.onBackPressed();
}

@Override
public void onRequestPermissionsResult(
int requestCode, @NonNull String[] permissions, @NonNull int[] grantResults) {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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);
Expand All @@ -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();
Expand All @@ -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),
Copy link
Contributor

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?

Copy link
Contributor Author

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.

// until setFrameworkHandlesBack is set to true.
activity.getOnBackPressedDispatcher().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();
}

Expand Down Expand Up @@ -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
Expand Down