You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some web application may require access to some resource on the device, such as camera, gps. Should there have some place to store the authorization information for these web apps to access such kind of resource, in the manifest.
In section 7.2, it is indicated that:
However, in designing these measures, implementors are advised to enable user awareness of information sharing, and to provide easy access to interfaces that enable revocation of permissions.
So, this kind of permission information might be better being stored in the local device?
Thanks!
The text was updated successfully, but these errors were encountered:
@wwumit although leveraging the manifest for enabling device APIs has been discussed a lot within the context of the W3C, currently there are no APIs that would make use of this feature.
I feel it would be premature to add this to the spec until we have a strong case to do so.
Some web application may require access to some resource on the device, such as camera, gps. Should there have some place to store the authorization information for these web apps to access such kind of resource, in the manifest.
In section 7.2, it is indicated that:
However, in designing these measures, implementors are advised to enable user awareness of information sharing, and to provide easy access to interfaces that enable revocation of permissions.
So, this kind of permission information might be better being stored in the local device?
Thanks!
The text was updated successfully, but these errors were encountered: