-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add optional permissions to manifest file #22
Comments
Great suggestion @mikekolganov, any chance you'd have time to submit a PR? |
Anyone up for this? |
This is desperately needed. There are so many sites that I would applicationize if they could display notifications. In the meantime, the following doesn't work for me. Even if the website has full permissions and ability to display notifications via chrome tabs, the applicationized version of the website has no permissions, and fails to prompt for them.
|
Either resolving #25 or submitting a PR to add optional permission support would resolve this issue. Anyone up for this? 👍 |
This has now been implemented in 006839b and 6ee2160 ! The following permissions can now be granted in the Advanced Options section of https://applicationize.me/now:
If there are any other permissions you would like to be able to control, let me know! 👍 |
Story: When Chrome asks user for permissions on regular tab (like notifications, access to camera and min) dialog is displayed at top of the page. But applicationized extensions isn't displayed these dialogs. And to enable notifications user needs to open applicationized website in regular tab to allow required permissions.
Suggestion: allow to choose permissions on generating applicationize under "Advanced" button. Not all, just common like
audioCapture
,videoCapture
,notifications
, etc. and put them to manifest file along withwebview
.Related to #13.
The text was updated successfully, but these errors were encountered: