- From: <bugzilla@jessica.w3.org>
- Date: Sat, 30 Apr 2011 16:25:02 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12577
Summary: Offline Web applications: we should discourage the
inclusion of the main page in the manifest
Product: HTML WG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: benjamin@webkit.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
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.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 30 April 2011 16:25:04 UTC