Bug 56133 - Binding HtmlWebViewSource in ContentPage causes menu stutter for MasterDetail
Summary: Binding HtmlWebViewSource in ContentPage causes menu stutter for MasterDetail
Status: RESOLVED ANSWERED
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.3.4
Hardware: PC Mac OS
: Highest normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-05-09 11:38 UTC by Rob Hedgpeth
Modified: 2017-06-29 16:28 UTC (History)
5 users (show)

Tags: webview, masterdetail, ac, xamexttriage, android
Is this bug a regression?: ---
Last known good build:


Attachments
WebViewMasterDetailIssue (60.19 KB, application/zip)
2017-05-09 11:38 UTC, Rob Hedgpeth
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description Rob Hedgpeth 2017-05-09 11:38:11 UTC
Created attachment 22027 [details]
WebViewMasterDetailIssue

When switching from Page1 to Page2 (see attached sample) there is an obvious stutter/delay when the menu (slide out) is automatically closed. The stutter/delay occurs when the HtmlWebViewSource is bound via XAML. This only happens on Xamarin.Form Android.
Comment 1 Paul DiPietro [MSFT] 2017-05-19 15:15:41 UTC
Setting to confirmed for further investigation. To me in the emulator it seems like the delay, albeit short, is the first time Page2 is tapped. Perhaps it's more significant on older devices?
Comment 2 Rui Marinho 2017-06-14 16:06:28 UTC
This doesn't seem to be a bug in Xamarin.Forms, just the time is taking to load the webpage depends on networdk/device etc.. Works ok on my LG nexus 5
Comment 4 David Ortinau [MSFT] 2017-06-15 19:25:28 UTC
This seems like a general Android issue, animating while rendering a WebView is bound to argue for resources, but I could be wrong. I'm not intimately familiar with our MDP implementation.

However, I'm also noticing a lot of Chromium errors when I run this.

https://gist.github.com/davidortinau/dcb99057f5f56602b89cfa8d808139e4

Moving this back to confirmed for further review and comment.
Comment 5 David Ortinau [MSFT] 2017-06-29 16:28:30 UTC
We have reviewed this further and don't seen anything Xamarin.Forms can do to change this.

The drawer animation is native, not a Xamarin.Forms controlled animation. 

The team recommendation is to address the sequencing of these two processes that compete for device resources.

- Load the WebView after the drawer is closed
- Load the WebView before closing the drawer