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 13355 - Split AppCache out
Summary: Split AppCache out
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: TrackerIssue
Depends on:
Reported: 2011-07-25 17:45 UTC by Mark Nottingham
Modified: 2011-08-29 17:18 UTC (History)
9 users (show)

See Also:


Description Mark Nottingham 2011-07-25 17:45:29 UTC
AppCache ("Offline Web applications") arguably is of a different maturity than the rest of HTML5. 

The impression I have is that takeup is lackluster (and some discussions I've had with browser vendors seem to confirm this), because it's not easy to use, and does not address the needs in this space well.

I'd propose that AppCache be split out into a separate document (either in the HTML5 WG or WebApps WG), to take it off of the critical path for HTML and allow it to either progress or evolve as necessary.
Comment 1 Anne 2011-07-25 17:48:56 UTC
Which browser vendor would this be? It's fully implemented in Opera, Firefox, Safari, and Chrome at least. And is being used out there for speeding things up.
Comment 2 Mark Nottingham 2011-07-25 17:53:35 UTC
I'm not disputing that it's being used, and I'm not at liberty to disclose private conversations. 

All I want this to do is start a discussion. If people really believe that AppCache is the future and a solid, fully-developed part of HTML, OK, but it seems to me it's at least worth a chat.
Comment 3 Aryeh Gregor 2011-07-25 20:57:28 UTC
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:

Status: Rejected
Change Description: no spec change
Rationale: AppCache has not been as successful as we'd like, but it appears to be stable and interoperably implemented.  If implementers are interested in dropping support, it can be marked at-risk and removed before or during the Candidate Recommendation stage.  If implementers want to make significant incompatible changes to it, so that it's no longer stable, that would be grounds to consider dropping it from HTML5 too.  Barring those circumstances, I see no reason to split it into a different spec.
Comment 4 Michael[tm] Smith 2011-08-04 05:16:39 UTC
mass-move component to LC1
Comment 5 Sam Ruby 2011-08-26 19:13:36 UTC
From the EDITOR'S RESPONSE "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"

Does anybody want to propose title and text for the tracker issue?  Or to
create the tracker issue themselves?
Comment 6 Mark Nottingham 2011-08-27 07:17:10 UTC
I think the original bug title and text here are adequate; do you need something else?
Comment 7 Sam Ruby 2011-08-29 17:18:12 UTC
Issue 173 raised: