- From: <bugzilla@jessica.w3.org>
- Date: Mon, 25 Jul 2011 20:57:29 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13355
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |Simetrical+w3cbug@gmail.com
Resolution| |WONTFIX
--- Comment #3 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 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:
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.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 25 July 2011 20:57:35 UTC