Change meaning of "IsLoadingToDifferentDocument" in WebContents to only
apply to loads in the main frame. The distinction between "IsLoading" and "IsLoadingToDifferentDocument" appears to only be relevant in UI contexts (e.g. TabRendererData, which controls whether to show the throbber in the tabstrip on desktop Chrome). I think the distinction only makes sense in the context of the main frame and a load in a subframe should always be lumped in with non-top-level document loads. For example, on Android it's sometimes used to conditionally call ToolbarLayout.onNavigatedToDifferentPage(), which from other callsites definitely appears to only care about main frame navigations. Making this change means the throbber won't flicker when content is loaded in an iframe right after the main frame finishes loading, which happens a lot (see bug). With this change, we can probably remove the timer added in 89603210 which attempts to smooth out favicon/throbber flickering. Bug: 734104 Change-Id: Ie14b1c54956479021fd9aa6c4c8aa690be52f193 Reviewed-on: https://chromium-review.googlesource.com/569060Reviewed-by:Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#486854}
Showing
Please register or sign in to comment