Bug 45685 – Web Inspector: Unclear which results are coming from the Cache

• Component: Web Inspector (Deprecated)
• Status: RESOLVED FIXED

[Annie Sullivan]

In addition to results that come from the network, in the resources panel, sometimes results from the cache are shown, and it's unclear at a glance which is which. HttpWatch shows cached results (this is a really useful feature), but it clearly differentiates between the two in the Result column (see attached screenshot).

It would also be good to do this for the HTML5 application cache.

[Pavel Feldman]

Created attachment 67575 [details]
[IMAGE] Visualization of cached resources.

We use visual notation for the cached resources (see screenshot attached) + there is a tooltip. We've recently supported resources cached by the network stack too. I'll rename this bug to address the missing AppCache part.

[Annie Sullivan]

In that screenshot, it looks like you need to hover over the resource to see that it came from the cache? I think it really needs to be obvious at a glance (different color or a column that says something like "(cache)".

[Pavel Feldman]

(In reply to comment #2)
> In that screenshot, it looks like you need to hover over the resource to see that it came from the cache? I think it really needs to be obvious at a glance (different color or a column that says something like "(cache)".

Cached resources' bars have transparent background + solid border. But I agree that we might need a more catchy distinction.

[Sreeram Ramachandran]

(In reply to comment #3)
> Cached resources' bars have transparent background + solid border. But I agree that we might need a more catchy distinction.

Yes, especially when sending screenshots of the waterfall, it's really hard to see the difference (there's no hover to help too). Perhaps you could increase the transparency of the fill and make the solid border darker?

[Annie Sullivan]

Yeah, it definitely needs to be clearer at a glance! Changing the bug title back.

[Alexander Romanovich]

Created attachment 82636 [details]
Google Chrome UI example

This is really awkward for developers. Would the Safari team consider adopting something like what Chrome is doing?  They state "(from cache)" in some of the web inspector columns. See attached screenshot.

[Alexander Romanovich]

I should also note that this isn't just a case of something missing that would be useful for developers. What Safari is showing now is actually incorrect. In the Safari instance of the above example, it states that a "200 OK" status code was received from the server for a request that never contacted the server in the first place.

[Michael Nordman]

It'd be nice if it said "from appcache" instead of "from cache" to distinguish between the HTTP cache and the APPCACHE.

[Alexey Proskuryakov]

Apple employees, see also <rdar://problem/9785591>.