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 18273 - Can the cache mode setting be made more clear in terms of the behaviour difference between fast and prefer-online (http://stackoverflow.com/questions/11263765/cache-manifest-what-is-the-prefer-online-setting)
Summary: Can the cache mode setting be made more clear in terms of the behaviour diffe...
Status: RESOLVED DUPLICATE of bug 18272
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:55 UTC by contributor
Modified: 2012-09-13 15:12 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2012-07-18 17:55:08 UTC 
This was was cloned from bug 17655 as part of operation convergence.
Originally filed: 2012-06-29 15:51:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-06-29 15:51:02 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html
Multipage: http://www.whatwg.org/C#writing-cache-manifests
Complete: http://www.whatwg.org/c#writing-cache-manifests

Comment:
Can the cache mode setting be made more clear in terms of the behaviour
difference between fast and prefer-online
(http://stackoverflow.com/questions/11263765/cache-manifest-what-is-the-prefer
-online-setting)

Posted from: 95.152.202.166
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
================================================================================
Comment 1 Robin Berjon 2012-09-13 15:12:53 UTC 

*** This bug has been marked as a duplicate of bug 18272 ***