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
I migrated as soon as possible the Firefox extension to MV3 for long-term purpose. But it seems that there is a non-standard behavior: Firefox uses host_permissions from package.json as optional. This is not the case with the Chromium world: optional permissions are optional. Chromium will automatically ask to approve or deny host_permissions on installation.
Also, you can't request a permission as you want:
To follow the principle of "no surprises", [some] APIs like this can only be called from inside the handler for a user action. User actions include the following:
Clicking the extension's browser action or page action.
Selecting a context menu item defined by the extension.
Activating a keyboard shortcut defined by the extension (this only treated as a user action from Firefox 63 onwards).
This behavior is clearly annoying because I already pushed 0.0.3 to Mozilla Addons store. I deactivated the release even if it was working if approving manually the permissions ; the store only gives the possibility to install 0.0.1 (firefox-mv2).
Solution
I am thinking about just asking to press a button to approve everything... But this is not optimal and I have no idea about how handle the removal of permissions at any time, I might need to monitor permissions change. Or just let the techy-users use the browser interface. Otherwise, it means implementing an options page with check-boxes because no one is going to open the settings and approve it manually. The actual green icon requesting for approval is not even visible/understandable.
User solution
Go in your extensions menu and right-click on the extension (or the gear) when using currently using Google Search/Google Translate proxy. Approve the right permission auto requested. You can approve more directly by managing the extension settings. Check official illustrations below.
lnoss
changed the title
Firefox MV3 extension host_permissions are considered as optional permissions and are not request by default on installation
Firefox MV3 extension host_permissions are considered as optional permissions and are not requested for approval automatically on installation
Dec 20, 2023
lnoss
changed the title
Firefox MV3 extension host_permissions are considered as optional permissions and are not requested for approval automatically on installation
Firefox MV3 extension host_permissions are considered as optional permissions and are not automatically requested for approval on installation
Dec 20, 2023
Also, runtime.onInstalled. Extension could open a tab with a grant permissions button with a callback to permissions.request(). No wonder people are tearing themselves apart between the two Manifest versions.
Workflows seem not stable, and I don't want to work on a extension interface to handle permissions. It should be more properly handled by the web browser.
Refs: #5, 748c278
Context
I migrated as soon as possible the Firefox extension to MV3 for long-term purpose. But it seems that there is a non-standard behavior: Firefox uses
host_permissions
frompackage.json
as optional. This is not the case with the Chromium world: optional permissions are optional. Chromium will automatically ask to approve or denyhost_permissions
on installation.Also, you can't request a permission as you want:
This behavior is clearly annoying because I already pushed 0.0.3 to Mozilla Addons store. I deactivated the release even if it was working if approving manually the permissions ; the store only gives the possibility to install 0.0.1 (firefox-mv2).
Solution
I am thinking about just asking to press a button to approve everything... But this is not optimal and I have no idea about how handle the removal of permissions at any time, I might need to monitor permissions change. Or just let the techy-users use the browser interface. Otherwise, it means implementing an options page with check-boxes because no one is going to open the settings and approve it manually. The actual green icon requesting for approval is not even visible/understandable.
User solution
Go in your extensions menu and right-click on the extension (or the gear) when using currently using Google Search/Google Translate proxy. Approve the right permission auto requested. You can approve more directly by managing the extension settings. Check official illustrations below.
Official illustrations
Documentation
The text was updated successfully, but these errors were encountered: