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 12577 - Offline Web applications: we should discourage the inclusion of the main page in the manifest
Summary: Offline Web applications: we should discourage the inclusion of the main page...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-30 16:25 UTC by Benjamin Poulain
Modified: 2011-08-04 05:04 UTC (History)
5 users (show)

See Also:

Attachments

Description Benjamin Poulain 2011-04-30 16:25:01 UTC 
In the introduction, one can find the following note:
"Authors are encouraged to include the main page in the manifest also, but in practice the page that referenced the manifest is automatically cached even if it isn't explicitly mentioned."

The problem is the following pattern I noticed for web applications:
-the web application uses a single document named index.html
-it is served as the default page of some directory e.g.: http://example.com/webapp/
-the manifest include index.html

This causes the user-agent to download the web application twice: once for '/', once for index.html

I think we should say instead that it is not required to list the document itself in the manifest.
Comment 1 Ian 'Hixie' Hickson 2011-06-21 05:40:21 UTC 
Well we should encourage the manifest to not include a URL that isn't the canonical URL, and then we should encourage authors to only have one URL per page, sure... but why would that mean not encouraging the explicit listing of the canonical URL?
Comment 2 Ian 'Hixie' Hickson 2011-08-01 22:19:15 UTC 
Also, having both files downloaded isn't a huge deal. The URL the author expects to be used is one that really must be cached, because that's the one that links will point to within the app (so if it's omitted and the user starts from a non-canonical URL, then while offline clicks on a link, then clicks back to the main page, it'd break if it wasn't cached).


EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: I don't really see the problem here.
Comment 3 Michael[tm] Smith 2011-08-04 05:04:12 UTC 
mass-moved component to LC1