The short reason for why WebExtensions can’t access new tab is that it would create a major security risk. The New Tab page is privileged browser code, not web content, so giving an extension access to that page would completely bypass the extension...
In general, I agree that we have a lot of room to improve on how we make recommendations, both in product and on AMO, especially in terms of knowing the user’s existing context.Since I’m not involved in running it, I don’t want to get into specific c...
Hi everyone! I wanted to provide a quick update on how this particular feature is coming along.At a high level, the ability to manage permissions on a per-site basis is part of the changes coming in Manifest v3 (MV3), which Chromium-based browsers a...
Hi folks! We're working towards shipping this feature, which depends on a much larger project. The ability to have optional permissions for a site is a new extension capability known as host permissions, that's a part of a major platform upgrade kn...
Hi there, thanks for your suggestion! This is something we will look at the next time we refresh this UX.In the meantime, there's a couple of workarounds, for add-ons that are hosted on AMO. First, the author name links to the author page for all o...
