This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18746 - Hi After trying out Offline Web Application features in several browsers (Opera, Chrome, Firefox) I unfortunately notice that none of them works the same, they are not compatible. As a web developer (not browser developer) I have some problems to deeply a
Summary: Hi After trying out Offline Web Application features in several browsers (Ope...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-30 15:32 UTC by contributor
Modified: 2012-11-16 18:51 UTC (History)
7 users (show)

See Also:


Attachments

Description contributor 2012-08-30 15:32:24 UTC
Specification: http://dev.w3.org/html5/spec/spec.html
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Hi

After trying out Offline Web Application features in several browsers (Opera,
Chrome, Firefox) I unfortunately notice that none of them works the same, they
are not compatible. As a web developer (not browser developer) I have some
problems to deeply and surely understand all aspects of the Offline Web
Application specification, so the problems might only be related to the
browser implementation, not the specification itself, but since a import goal
of HTML5 is that the browsers should be compatible, I provide a list of the
problems here:

Opera doesn't load ajax requests from the application cache. Chrome and
Firefox do.
I think that "5.7.6 Changes to the networking model" states that it should be
done.

When navigating from a webpage (with manifest) to another webpage (without
manifest), where the second webpage was in the first pages manifest, all
browsers fetch the second webpage from the application cache.
But Opera and Firefox set window.applicationCache.status as UNCACHED, while
Chrome handles the window.applicationCache.status as active, that is IDLE.
While reading "5.7.5 The application cache selection algorithm" bullet two
seams to state that the application cache shall be active for the Document.

I can of course provide sample code for the situations if requested.

Best Regards
Fredrik Persson

Fredrik.Z.Persson@ericsson.com
This Communication is Confidential. We only send and receive email on the
basis of the terms set out at www.ericsson.com/email_disclaimer  

Posted from: 194.237.142.20
User agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.83 Safari/537.1
Comment 1 Ian 'Hixie' Hickson 2012-11-05 23:55:04 UTC
My recommendation would be to file bugs on those browsers. I don't think there's much that can be done in the spec to clarify these particular issues.

cc'ing zcorpan, jgraham, bz, roc, ms2ger for opera and gecko in case they want to file bugs themselves.