| Index: content/browser/renderer_host/render_view_host_impl.cc
|
| diff --git a/content/browser/renderer_host/render_view_host_impl.cc b/content/browser/renderer_host/render_view_host_impl.cc
|
| index 68204fb746a36dc3416fb2428238d013f2a5c689..01e60edcb5b1180cbd24101298cb3d7c97c6ab5f 100644
|
| --- a/content/browser/renderer_host/render_view_host_impl.cc
|
| +++ b/content/browser/renderer_host/render_view_host_impl.cc
|
| @@ -332,20 +332,6 @@ void RenderViewHostImpl::Navigate(const ViewMsg_Navigate_Params& params) {
|
| Send(new ViewMsg_Navigate(GetRoutingID(), params));
|
| }
|
|
|
| - // Force the throbber to start. We do this because WebKit's "started
|
| - // loading" message will be received asynchronously from the UI of the
|
| - // browser. But we want to keep the throbber in sync with what's happening
|
| - // in the UI. For example, we want to start throbbing immediately when the
|
| - // user naivgates even if the renderer is delayed. There is also an issue
|
| - // with the throbber starting because the WebUI (which controls whether the
|
| - // favicon is displayed) happens synchronously. If the start loading
|
| - // messages was asynchronous, then the default favicon would flash in.
|
| - //
|
| - // WebKit doesn't send throb notifications for JavaScript URLs, so we
|
| - // don't want to either.
|
| - if (!params.url.SchemeIs(kJavaScriptScheme))
|
| - delegate_->DidStartLoading(this);
|
| -
|
| FOR_EACH_OBSERVER(RenderViewHostObserver, observers_, Navigate(params.url));
|
| }
|
|
|
|
|