stig
July 9, 2022, 7:28pm
6
After my initial attempt to get some MV3 experience with one of my extensions , I slowly start to realize your plans when it comes to handling host-permissions…
zombie:
We’re adding UI to make it easier for users to understand what host permissions an extension needs/has, and to grant/revoke them:
Ability to grant host permissions from the browser action context menu since bug 1769793 landed in Nightly a few days ago.
Ability to run content scripts for the current site when clicking the the browser action, bug 1774641 to land this week in Nightly.
We’re also working on similar affordances for extensions which don’t have a browser action button, and also on ability for users to choose to grant permissions at install time (though they will explicitly need to opt-in for extensions that list <all_urls> ).
So if I have an extension specifically constructed for flickr.com , the user cannot grant the host permission (solely) for flickr.com already at install time. But will have to do it on next visit to flickr.com ? Sorry, but that sounds kind of lame to me.
Does Google do the same?
1 Like