W3C home > Mailing lists > Public > public-coremob@w3.org > June 2012

Re: coremob-ISSUE-1: AppCaches fix planned for HTML.next only [COREMOB-1]

From: Charles McCathieNevile <chaals@opera.com>
Date: Tue, 19 Jun 2012 09:14:53 +0200
To: public-coremob@w3.org, "Core Mobile Web Platform Community Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.wf42e3slwxe0ny@widsith-3.local>
On Mon, 18 Jun 2012 18:34:25 +0200, Core Mobile Web Platform Community  
Group Issue Tracker <sysbot+tracker@w3.org> wrote:

> coremob-ISSUE-1: AppCaches fix planned for HTML.next only [COREMOB-1]
>
> http://www.w3.org/community/coremob/track/issues/1
>
> Raised by: Tobie Langel
> On product: COREMOB-1
>
> Some critical AppCache issues  
> (https://www.w3.org/Bugs/Public/show_bug.cgi?id=14702) are being fixed  
> (http://html5.org/tools/web-apps-tracker?from=7135&to=7136) in the HTML  
> Living Standard spec. Unfortunately, these fixes aren't brought (yet) to  
> the HTML5 spec because they are considered new features belonging in  
> HTML.next. What should the group's position be with regards to that?

Why would this group care where the spec starts? What matters is to have a  
stable intereoperable spec, so it is more important to clarify that  
something is a requirement for this group, and there is interest (and  
effort offered??) in getting it stabilised.

Which then means figuring out what is the shortest route to that path -  
hint: do work...

cheers

Chaals

-- 
Charles 'chaals' McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg kan noen norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Tuesday, 19 June 2012 07:15:27 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 April 2013 17:36:46 UTC