-
Notifications
You must be signed in to change notification settings - Fork 936
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
WebView with back navigation transition doesn't work properly. #107
Comments
I have the same problem. I think it's because you are using WebviewScaffold and WebviewScaffold is using rectangle to launch the Webview. With that said it can't dynamically change it's position when using back button, only close and dispose Webview when page is disposed. I override back button to close and dispose Webview and then close the page. |
Also running into this. It is a significant contributor to jank. Is there anything that can be done about it? |
I also had this |
Here is an example showing what appears to be the native web view coming on screen before the view has slid on. Would it be possible to add a property to the web view that is a delay before rendering? Would it be possible to put a Flutter widget that shows the last view of the web view so that it can be animated in and out of the viewport? |
Same issue for me :( |
Hello, Any update on this? |
Same issue here. A workaround for navigating back for me was to use a class WebviewTest extends StatelessWidget {
final String url;
const WebviewTest({@required this.url});
@override
Widget build(BuildContext context) {
return WillPopScope(
onWillPop: () async {
FlutterWebviewPlugin().close(); // Close the plugin so that it doesn't overlay anymore
return true;
}
child: WebviewScaffold(
appBar: AppBar(
title: Text("Webview"),
),
url: url,
),
);
}
} This will, however, show your "loader" widget briefly (if unassigned, a regular |
This worked for me, however I had to make sure I am calling |
After pushing to WebView and then try to back (using iOS swipe), the transition doesn't work properly.
The text was updated successfully, but these errors were encountered: