635973 - Offline Application Caching and Cache Manifest should log errors when bailing

Status: RESOLVED DUPLICATE of bug 807501

(Core :: Networking: Cache, defect)

Description

[Austin King [:ozten]]

Fx4b11 Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11

As a web developer, I find this feature hard to test (or buggy).
Assumptions:
* Work Offline would be a fine way to test
* Pasting and Go, refresh, and hard refresh while offline should all show offline content

1) Load a webapp with a cache.manifest (Example [1] or [2])
Note: Prompted for offline access, so far so good :)

Load this into 3 tabs (for steps 3, 4, and 5 below).

2) File > Work Offline
3) Hit Refresh button 

Actual - No change
Expected - Offline behaviors

4) Paste url and hit enter into location bar

Actual - No change
Expected - Offline behaviors

5) Hard refresh

Actual - No change
Expected - Offline behaviors

6) File > Uncheck Work Offline
7) Disable networking (for operating system)

8) about:cache - 0 entries in offline cache

Repeat 3, 4, 5, 8
Step 3 - Server Not Found
4 - Offline content shown
5 - Server Not Found

Once steps 3 or 5 have happened, a currently opened tab to test step 4 is also reset to "Server not found".

[1] http://www.html5laboratory.com/s/offline-application-cache.html
[2] http://getting.shitdone.org/

Comment 1

[Honza Bambas (:mayhemer)]

Austin, for the link [1] I am unable to reproduce any problem.  For the letter it seems that -something- doesn't work.  I'll check that out, please don't modify the test case if you can!

To make it clear, what all exactly means for you "Offline behaviors" ?

To be honest, it is hard to debug problems with offline caching.  We are not doing much error reporting and I find it my self not very convenient for web developers having more complex offline web apps to figure out what's wrong.  I agree there have to be done something about it.

Comment 2

[Austin King [:ozten]]

(In reply to comment #1)
Offline behaviors - Basic - the page should load. Loading via address bar or refreshing the page should not show the "Server not found" error page.

Comment 3

[Austin King [:ozten]]

I've determined what is going on.

In my manifest I had resources that were directories and not files.

Once I trimmed down my manifest to only resources (html, css, js, etc), caching is working better.

New Expected Behavior:
The JS Console should log an error when the code that caches resources from the manifest encounters and error and bails.

This logging should happen for any conditions that cause caching to "give up".

Comment 4

[Honza Bambas (:mayhemer)]

(In reply to Austin King [:ozten] from comment #3)
> New Expected Behavior:
> The JS Console should log an error when the code that caches resources from
> the manifest encounters and error and bails.
> 
> This logging should happen for any conditions that cause caching to "give
> up".

bug 807501