[Android WebView] Provide user-initiated provisional load detection

[Android WebView] Provide user-initiated provisional load detection

Do not synthesize page loading events on DOM modification, if the provisional
load has been started from the API side.

It appears that a lot of apps tend to use the following scenario:

webView.loadUrl(...);
webView.loadUrl('javascript:...');

Which was triggering page loading events to be emitted. This scenario is
dubious, as no one guarantees that loading will actually finish prior to
executing javascript. But for compatibility reasons we must take it into
account and not emit page loading events for "about:blank", as it seems
that some apps do unexpected things when they receive it.

BUG=458569, 469099
Committed: https://crrev.com/7a3234c9a19a38726a4a984ff12e2b406423c1d3
Cr-Commit-Position: refs/heads/master@{#321857}

[mnaganov (inactive), 2015-03-20 17:01:50]

mnaganov@chromium.org changed reviewers:
+ torne@chromium.org

[Torne, 2015-03-23 11:34:26]

Not 100% sure that "user-initiated" is the right way to describe this; it's
"everything not initiated from the WebView API", right? Including JS-initiated
navigations/popups/etc?

[mnaganov (inactive), 2015-03-23 11:45:09]

On 2015/03/23 11:34:26, Torne wrote:
> Not 100% sure that "user-initiated" is the right way to describe this; it's
> "everything not initiated from the WebView API", right? Including JS-initiated
> navigations/popups/etc?

Correct, the name wasn't precise enough. Changed to
`StartedNonApiProvisionalLoadInMainFrame`.

[Torne, 2015-03-23 12:17:24]

lgtm

[mnaganov (inactive), 2015-03-23 12:43:41]

The CQ bit was checked by mnaganov@chromium.org

[commit-bot: I haz the power, 2015-03-23 12:44:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1024103002/20001

[commit-bot: I haz the power, 2015-03-23 12:50:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-03-23 12:50:07]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[mnaganov (inactive), 2015-03-23 13:02:25]

mnaganov@chromium.org changed reviewers:
+ sievers@chromium.org, tedchoc@chromium.org

[mnaganov (inactive), 2015-03-23 13:02:26]

Argh, need OWNERs approvals for changes in NavigationEntry.

tedchoc@: can you please take a look at chrome/android/javatests
sievers@: can you please take a look at content/

[Ted C, 2015-03-23 17:39:35]

On 2015/03/23 13:02:26, mnaganov (cr) wrote:
> Argh, need OWNERs approvals for changes in NavigationEntry.
> 
> tedchoc@: can you please take a look at chrome/android/javatests
> sievers@: can you please take a look at content/

chrome/android/javatests - lgtm

[no sievers, 2015-03-23 18:34:38]

content lgtm

[mnaganov (inactive), 2015-03-23 21:24:01]

The CQ bit was checked by mnaganov@chromium.org

[commit-bot: I haz the power, 2015-03-23 21:24:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1024103002/20001

[commit-bot: I haz the power, 2015-03-23 21:29:08]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-03-23 21:30:15]

Patchset 2 (id:??) landed as
https://crrev.com/7a3234c9a19a38726a4a984ff12e2b406423c1d3
Cr-Commit-Position: refs/heads/master@{#321857}