diff options
| author | mnaganov <mnaganov@chromium.org> | 2015-03-23 14:28:59 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-03-23 21:30:06 +0000 |
| commit | 7a3234c9a19a38726a4a984ff12e2b406423c1d3 (patch) | |
| tree | 565d43f11238ce6e2c79c7ce56957d36c784796b /android_webview/OWNERS | |
| parent | 03b770885dbf8d873c38f72b98fd4faddf80633e (diff) | |
| download | chromium_src-7a3234c9a19a38726a4a984ff12e2b406423c1d3.zip chromium_src-7a3234c9a19a38726a4a984ff12e2b406423c1d3.tar.gz chromium_src-7a3234c9a19a38726a4a984ff12e2b406423c1d3.tar.bz2 | |
[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
Review URL: https://codereview.chromium.org/1024103002
Cr-Commit-Position: refs/heads/master@{#321857}
Diffstat (limited to 'android_webview/OWNERS')
0 files changed, 0 insertions, 0 deletions