-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empowered apps #58
Comments
This talk discusses how to grant access to powerful features . One approach I've seen discussed in the Device and Sensors WG is semantic permission bundles, which could group together multiple related permissions under one user prompt. There is also a proposal from Microsoft for granting permissions for PWAs at install time. See: |
I think it would be great if permissions could be granted/revoked/denied programmatically when running automated tests. I just found out that there is a Browser Testing and Tools Working Group. Maybe this is of interest for them. So far there are some flags one can set when starting Chromium browsers or Firefox but they are not very well documented. At least to my knowledge this page is the most extensive list of Chromium flags which may or may not work any longer. It's also possible to change permissions via the Chrome DevTools Protocol. It has experimental support for a Browser.grantPermissions and Browser.resetPermissions method. All browsers allow to manually grant or revoke permissions but that doesn't really help when running automated tests. |
I generally agree. What are some examples we can think of for permissions that would be useful? |
Professional applications need to access lower level features, which cannot be exposed on the Web at large to avoid abuse by malicious sites. What mechanism could be used to allow for a different trust model for certain apps?
Raised in:
The text was updated successfully, but these errors were encountered: