W3C home > Mailing lists > Public > public-html-comments@w3.org > August 2011

Re: appcache & link relation

From: Yves Lafon <ylafon@w3.org>
Date: Thu, 4 Aug 2011 06:04:32 -0400 (EDT)
To: Henri Sivonen <hsivonen@iki.fi>
cc: public-html-comments@w3.org
Message-ID: <alpine.DEB.1.10.1108040558450.1244@wnl.j3.bet>
On Thu, 4 Aug 2011, Henri Sivonen wrote:

> On Wed, 2011-08-03 at 16:03 -0400, Yves Lafon wrote:
>> In http://www.w3.org/TR/2011/WD-html5-20110525/semantics.html#attr-html-manifest
>> linking to a manifest is done via an attribute and not using something
>> like
>> <link rel="appcache.manifest" href="<manifest-URI>">
>> The <link> based approach would allow better upgrade mechanism, if the
>> format of the manifest changes, for exemple.
>
> [Disclaimer requested by the Chairs: This is not an official response
> from the working group. This is my personal response.]
>
> <link> doesn't work because of
>
> <!DOCTYPE html>
> <script src=script.js></script>
> <!-- event loop spins -->
> <link rel=appcache.manifest" href="manifest.manifest">

Well, there is an 'update()' call that triggers the application cache 
download process, and when called, is done after the event loop spins, so 
if it fails for <link>, it should also fail for a direct 'update' call, no?

-- 
Baroula que barouleras, au tiƩu toujou t'entourneras.

         ~~Yves
Received on Thursday, 4 August 2011 10:04:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 4 August 2011 10:04:34 GMT