Barstow; public-webapps
Subject: RE: [manifest] RE: Manifest for web application; review deadline March
5
Yes, indeed. I just didn´t remember the final name.
Does that cover your first question?
Regarding the second questions, Anssi wrote an extension spec:
http://w3c.github.io/manifest-csp/
He
Hi Claes,
The web app manifest spec allows extensions (it has extension points), so
we would expect the Permissions WG/CG to come up with a proper way to deal
with permissions. If they come to the conclusion that we need some
permission field in the manifest, their spec can add that. It is not
height_Email_144dpi
*From:*Christiansen, Kenneth R [mailto:kenneth.r.christian...@intel.com]
*Sent:* den 6 mars 2015 10:46
*To:* Nilsson, Claes1; 'Kenneth Rohde Christiansen'; Kostiainen, Anssi; Arthur
Barstow; public-webapps
*Subject:* RE: [manifest] RE: Manifest for web application; review deadline
March 5
] RE: Manifest for web application; review deadline March
5
Hi Claes,
The web app manifest spec allows extensions (it has extension points), so we
would expect the Permissions WG/CG to come up with a proper way to deal with
permissions. If they come to the conclusion that we need some permission
Hi,
We support that this version of the specification is moved to Candidate status
but we have a few comments/questions:
In this version 1 we miss:
* A permissions field
* A content security policy field. This is only included as a way to state
allowed origins from which the manifest file
