Can we prevent addons from opening a firstrun page?
Categories
(WebExtensions :: General, enhancement)
Tracking
(Not tracked)
People
(Reporter: mkaply, Unassigned)
Details
One of the most common complaints in the enterprise space with addons is that when they are installed via policy, a lot of addons open a welcome page.
I've been asked if we can implement a policy that prevents this.
What I was picturing is some mechanism that prevents tab.create during the onInstalled of addons.
Is this possible?
(I know, obvious answer is for addons to add enterprise policy to flip this off, and I've been able to get one to do it, but it's an uphill battle.)
|
||
Comment 1•4 years ago
•
|
||
I don't think we can really do that:
- Some of the addons don't use the onInstalled event, but instead open tabs after some (async) setup is done, like downloading of some data or configuration. And if we started doing it, they could switch to a setTimeout which we couldn't detect.
- We have a requirement that addons inform the user about their (privacy) policy, and most do it onInstall, so blocking that seems wrong.
Your best bet is probably to reach out to developers of such extensions, and they could avoid opening the first run when configured via storage.managed or similar.
|
Reporter | |
Comment 2•4 years ago
|
||
Totally fair. Just thought I would bring it up. I have been reaching out to developers of those extensions.
I also wondered about mapping storage to storage.managed without the addon being involved...
Description
•