NetworkService: Displayed LoadInfo doesn't display when an extension is blocking a request, or non-network request status |
|||||
Issue descriptionWhen the network service is enabled, only the status of requests managed by the NetworkService is displayed, and only net's knowledge about them is used. This means that requests that don't use the network service (file URLs, ServiceWorker) can't be displayed, nor the status of requests that haven't yet made it to the network service (Like if an extension is slowing a request down, as it decides what to do with it), and requests that are blocked on an extension while in some intermediary state (Like deciding if they should follow a redirect) just display "Processing Request". I'm not sure how much effort we want to invest in improving things here, but thought I'd file a bug for tracking purposes.
,
Aug 13
No, it refers to the little loading info at the bottom left of the browser ("Waiting for cache" / "Connecting..." / "Waiting for www.foo.com" / etc).
,
Aug 13
Actually, the situation is worth than I was thinking - we'll actually display incorrect information if the only resources for a page are not being handled by the network service (We'll display whatever was the last information we received from the network service, and never update it, until some resource is handled by the network service).
,
Aug 13
[+jam]: Just FYI. This shouldn't block Canary, but doing something about this should perhaps block stable.
,
Aug 14
Thanks for filing. Note that most of these messages might be going away as part of bug 873307.
,
Aug 14
,
Aug 30
Moving this out of ServiceWorker's triage queue by making it Available.
,
Oct 10
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by falken@chromium.org
, Aug 13