13355 2011-07-25 17:45:29 +0000 Split AppCache out 2011-08-29 17:18:26 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED WONTFIX TrackerIssue P2 normal --- 1 mnot ian annevk art.barstow ayg julian.reschke mike public-html-admin public-html-wg-issue-tracking rubys w3c public-html-bugzilla oldest_to_newest 51448 0 mnot 2011-07-25 17:45:29 +0000 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. 51449 1 annevk 2011-07-25 17:48:56 +0000 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. 51450 2 mnot 2011-07-25 17:53:35 +0000 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. 51456 3 ayg 2011-07-25 20:57:28 +0000 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: 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. 53716 4 mike 2011-08-04 05:16:39 +0000 mass-move component to LC1 55893 5 rubys 2011-08-26 19:13:36 +0000 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? 55908 6 mnot 2011-08-27 07:17:10 +0000 I think the original bug title and text here are adequate; do you need something else? 55989 7 rubys 2011-08-29 17:18:12 +0000 Issue 173 raised: http://www.w3.org/html/wg/tracker/issues/173