is the app in question available somewhere to be able to reproduce?

Hello,
Yes, the application is AlAhliMobile, it is in the PlayStore.
*The steps to reproduce* the issue are:
1.- Download and install the app AlAhliMobile
*2.- In the first screen do tap on the "New user registration" button.*
Then the options are 2:
*2.1.- The screen will be white, then move to background and return to the
app(The screen will be shown correctly)*
2.2.- If the screen is shown correctly, close the app and return to step
(2.)

Thank you in advance.
Best regards

2016-05-19 14:54 GMT+02:00 timvolodine@chromium.org via Monorail <
monorail@chromium.org>:

Hello,

Are you investigating the issue?
Thank you in advance.

Best regards

test team can you do a bisect on that?

sgurun@ sure we will bisect and update soon.

This issue not reproducible on samsung S5 (LRX21T) having both web view 50.0.2661.66 , 50.0.2661.86 and 51.0.2704.61 with app AlAhliMobile(2.4.0) following the steps mentioned in comment#3 on 2G,3G and 4G. I was able to see once on 4G but after few seconds it navigated the page content. 

Have you tried 50.0.2661.89?

I wonder if we break sth from .86 to .89 (unlikely) or simply not repro for us?

Without a repro we cannot debug it, so will have to close the bug.

actually nevermind, .86 was broken according to #1

reporter: do you still see the issue? or did you fix it somehow in your app.

Hello,
The issue persist:
I have attached a video which is showing the issue, also I have attached the version of WebView(50.0.2661.86)
The issue happens randomly, is not always happening.
Thank you in advance.
Best regards.

Deleted: Samsung_S6_edge_webviewV_50.0.2661.86.jpg 340 KB

	Samsung_S6_edge_webviewV_50.0.2661.86.jpg 340 KB View Download

Deleted: Samsung_S6_edge_webviewV_50.0.2661.86_AlAhliMobile.mp4 4.0 MB

Samsung_S6_edge_webviewV_50.0.2661.86_AlAhliMobile.mp4 4.0 MB Download

Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hello,

For more info:
When I am going to show the page, the call for the function is this:
CODE: window.open(url, '_blank', options);
WHERE "options" are: "location=no,toolbar=no,hidden=yes,clearcache=yes,clearsessioncache=yes,disallowoverscroll=yes"
It has to be taken into consideration that the "hidden" parameter is setted to "true".
It seems that if I change the "hidden" parameter to "false" the page is showing correctly.

Thank you in advance.

Hello,

Do you need anything more to fix the issue?

Thank you in advance.

Hi, Did this issue only happen on Samsung S5?

We can't reproduce this issue, if you get the white screen again, could you try to connect to WebView by developer tools to see if you can find any issue?

Hello,

In developer tools all is running correctly.
I tested in 2 devices more. 
   HTC One with Android 6.0(WebView: 50.0.2661.86)
   Samsung S4 with Android 5.0.1(WebView: 50.0.2661.86)
Is happening the same.
Please, find attached videos.

Thank you.
Beste regards

Deleted: HTC_One_Android_6.0.mp4 2.4 MB

	HTC_One_Android_6.0.mp4 2.4 MB View Download

Deleted: Samsung_S4_Android_5.0.1.mp4 2.9 MB

	Samsung_S4_Android_5.0.1.mp4 2.9 MB View Download

Deleted: HTC_One_Android6.0-Samsung_S4_Android5.0.1.jpg 1.0 MB

	HTC_One_Android6.0-Samsung_S4_Android5.0.1.jpg 1.0 MB View Download

Bo, would getting a trace help here? any ideas for debugging?

yeah, trace with all default categories + cc.debug

https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs#TOC-Capture-a-trace-from-Chrome-on-Android-with-DevTools-

I'm seeing a similar thing with our app (https://play.google.com/store/apps/details?id=com.geddup.app.android&hl=en)
Trying to get a trace is proving tricky as attaching the inspector (chrome://inspect/?tracing#devices) seems to stop the behaviour from happening, and for us it occurs very soon after app start.

Inspecting without tracing gives me a better chance of triggering the issue, but usually it also causes the issue to disappear. There are no errors in the devtools console that could indicate what is happening.

I've observed 3 points that are interesting about this issue:

- watching the page changes from the inspect overview page (chrome://inspect/#devices) shows the webview moving between the expected pages

- the webview contents are invisible but still clickable, so managing to click an item that causes a page reload or DOM change can be enough to cause the view to render

- rarely the webview contents won't be invisible, but rather, corrupted. I've attached an image which shows this

We are seeing this on:

- Nexus 4 running 5.1.1 (LMY48T) with Chrome webview 51.0.2704.36
- Nexus 5X running N (NPD35K) with Chrome webview 51.0.2704.36

Deleted: 2016-06-12 03.18.46.png 66.1 KB

	2016-06-12 03.18.46.png 66.1 KB View Download

I've been looking at this further, and for my issue, it looks like this has been sorted out somewhere between 51.0.2704.43 and 51.0.2704.54. From my testing, looking at all versions of com.google.android.webview I could find, only the following caused the issue on my devices:

 50.0.2661.59 (266105900)
 50.0.2661.59 (266105950)
 50.0.2661.66 (266106600)
 50.0.2661.66 (266106650)
 50.0.2661.86 (266108600)
 50.0.2661.86 (266108650)
 51.0.2704.28 (270402800)
 51.0.2704.28 (270402850)
 51.0.2704.36 (270403600)
 51.0.2704.36 (270403650)
 51.0.2704.36 (275503650)
 51.0.2704.43 (270404350)

I'm getting spinner that doesn't disappear on webview built from trunk

what's the spinner waiting for?

The spinner is waiting for a web request.
Maybe the service is down.
Please, check it later.
Thank you.

Hi folks, I believe this is the same issue we are seeing with the built-in SMS app (Messages) on a Samsung Galaxy S6 that we just bought for testing because of multiple reports by CrankWheel users.

Any link that is sent to you by SMS and you open in Samsung's Messages will show a blank page until you change orientation of your mobile screen, or poke the screen and happen to click somewhere where there was a link.

This did not happen when the phone was fresh out of the box and had version 46.0.2490.76 of Android WebView. We then allowed it to update Android WebView and received version 52.0.2743.98, which exhibits the problem.

Reproduction steps are simple:
1. Send an SMS to the phone with a URL to any web page; try something dead simple like an HTML-only page to verify that this is not a CSS or JavaScript issue.
2. Click the link you receive.

Expected: Should see the web page.
Actual: See a blank page.

I believe this is a widely occurring issue and not limited only to the Galaxy S6, although not frequently reported. Here are some reports we did manage to find that may be the same underlying issue, both of them reported on Galaxy S7 Edge phones:

http://forum.xda-developers.com/s7-edge/help/help-text-message-links-t3431119

https://github.com/facebook/react-native/issues/8593

Another report that may be the same underlying issue: https://plus.google.com/109655533802578930112/posts/X8CzHBY8wfT

#26 seems unlikely since they reported that on M50.

The issue described in #25 sounds like the same thing as b/30824239 which samsung are reporting as a regression in 52 - if so then it's unlikely to be the same as this bug as that's only in 52 and specific to samsung's particular app, but we're investigating it.

@torne, thanks for the additional information. Do you know if there is a public tracker anywhere for b/30824239?

Not currently, and we haven't determined yet if it's a webview bug or a problem with samsung's app; we'll file a crbug when we have more info, or reuse one of these if it turns out to be related.

the "wrapper-container" div has class="transparent", which is hiding all of the content, that's problem in your html, not webview