New issue
Advanced search Search tips

Issue 884172 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 883561
Owner: ----
Closed: Sep 21
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Usage of 'Size' column for '( from ServiceWorker)'

Reported by mayurar...@gmail.com, Sep 14

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Inspect the network tab for any app that uses a service worker 
2. Look at the 'size' column
3. Any request fulfilled by the service worker has '(from:ServiceWorker)' under the 'Size' column

What is the expected behavior?

What went wrong?
Why is the 'size' column the indicator of whether a request was fulfilled by a service worker or not ? A request fulfilled by a service worker could have been fetched from the network as well ( network only , cache-first / cache - else - network ) and not necessarily the cache API. 

The 'size' column should reflect the amount of data that was sent to the browser from sever for parsing.

If you show the actual size for requests fetched from the network at least, I can distinguish between requests fetched from the Cache API and the network .

I can still understand '(from disk cache)' appearing under 'Size' since there's no chance of network being involved , but the same is not true for service workers.Even from cache the size is interesting, eg "how much JS am I sending to the parser ?"

Did this work before? No 

Chrome version: 68.0.3440.106  Channel: n/a
OS Version: OS X 10.13.6
Flash Version: 

This will help provide clarity around requests intercepted by service workers.
 
Screen Shot 2018-09-14 at 6.03.03 PM.png
205 KB View Download
Components: Blink>ServiceWorker
Labels: -OS-Mac
Status: Untriaged (was: Unconfirmed)
Right now, in the full view, we list both transfer size (eg gzipped) & size. When it's "from cache" we remove both values. This seems wrong. The transfer size is 0 when it's from the cache, but we shouldn't remove overall size.

The same is true if it's from a service worker.
Possibly a dupe with bug 883561.
Mergedinto: 883561
Status: Duplicate (was: Untriaged)
(SW bug triage)

Yeah, looks like a dup with bug 883561.

Sign in to add a comment