On 04/07/13 12:50, Marcos Caceres wrote:
> ## Outstanding issues
> If version is greater than the highest version number supported by the user
> agent, should the user agent treat the manifest as the highest manifest
> version it supports? Or reject the manifest outright as invalid?
I think the application should be marked as incompatible. Imagine I have
an old phone with a runtime that only understand manifest_version { 0,
1, 2 }. My phone doesn't supports newer versions but there are newer
versions out there like { 3, 4, 5 }. If an application is advertising
itself as manifest_version = 3, it is a hint that my phone will not be
able to run it. It *might* be able to run it but nothing is less sure.
> If a manifest version number is invalid (i.e., NaN, <= 0 ), is the manifest
> invalid?
I think we should use manifest_version = 0 as the current default
version. Hopefully no one will ever write manifest_version = 0 because
we would introduce that feature at the same time as we would introduce
manifest_version = 1.
Also, I would like to think about the path to standardisation. Google
Chrome Apps have the same concept (manifest_version) using numbers too.
Should we have a special token like "w3c" or "standard" that will be
required to use the standard manifest version? I think that would be
reasonable even though that means that if some applications were using
"w3c" as a value, it might break them :(
--
Mounir
_______________________________________________
dev-webapps mailing list
dev-webapps@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-webapps
