https://www.w3.org/Bugs/Public/show_bug.cgi?id=28158
Bug ID: 28158
Summary: [Custom]: inflexible extends as fixed element type
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Sever
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28157
Bug ID: 28157
Summary: [Shadow]: Link to CSS Scoping module spec?
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: nor
On 2015-03-06 10:55, Nilsson, Claes1 wrote:
Yes, that covers my first question. I have also seen Anssi’s CSP extension
specification. I guess that the approach is to see how far we can get in the
Trust&Permissions CG on the ideas we experimented with for FFOS, i.e. to find a
way to securely o
Yes, that covers my first question. I have also seen Anssi’s CSP extension
specification. I guess that the approach is to see how far we can get in the
Trust&Permissions CG on the ideas we experimented with for FFOS, i.e. to find a
way to securely open up sensitive APIs to server hosted web site
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 can probably comment on that.
Kenneth
From: Nilsson, Claes1 [mailto:claes1.nils...@sonymobile.com]
Sent
Ok thanks Kenneth. I assume that you refer to the Trust & Permissions Community
Group, https://www.w3.org/community/trustperms/?
BR
Claes
Claes Nilsson
Master Engineer - Web Research
Advanced Application Lab, Technology
Sony Mobile Communications
Tel: +46 70 55 66 878
claes1.nils...@sonymobil
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 yet
