W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [manifest] Is the Webapp Manifest spec ready for FPWD?

From: Tobie Langel <tobie@fb.com>
Date: Mon, 4 Jun 2012 20:31:41 +0000
To: Fabrice Desre <fabrice@mozilla.com>, public-webapps <public-webapps@w3.org>
Message-ID: <CBF2E5E1.852B0%tobie@fb.com>


On 6/4/12 9:16 PM, "Fabrice Desre" <fabrice@mozilla.com> wrote:

>On 06/04/2012 10:38 AM, Tobie Langel wrote:
>> On 6/4/12 6:41 PM, "Fabrice Desre" <fabrice@mozilla.com> wrote:
>>
>>> Hi Tobie,
>>>
>>> On 06/04/2012 03:03 AM, Tobie Langel wrote:
>>>> On 6/2/12 6:54 AM, "Fabrice Desré" <fabrice@mozilla.com> wrote:
>>>>> We're working on pre-loading the appcache at install time when the
>>>>> appcache path is specified in the manifest. See
>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=702369 for the b2g
>>>>> support,
>>>>> and https://bugzilla.mozilla.org/show_bug.cgi?id=753990 for desktop
>>>>> support.
>>>>
>>>> That sounds nice. How do normal web pages link to their own config
>>>> file? I
>>>> haven't seen that mentioned in the spec draft.
>>>
>>> What do you call the config file here?
>>
>>The Web Application Manifest. (Sorry for the confusion, the Widget
>>spec calls roughly the same thing a configuration document.)
>>
>
>It's not linked directly in a <link> or other tag, but passed as a
>parameter to the .install() method.

Right, in the app store model. Surely, you're also planning to support
background installs of apps when visiting the apps URL in conjunction with
AppCache. In this case, how will the Web Application Manifest work? How
will it be referenced by the document? Are you planning on something like:

    <html webapp_manifest=path/to/config.webapp
manifest=path/to/manifest.appcache>

--tobie
Received on Monday, 4 June 2012 20:32:09 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT