Require permissions to install service workers and make it very visible when they are running

[ptramsey]

Right now, visiting a website can be sufficient to effectively install an invisible background service that runs so long as the browser is running (or, on Windows, even when the browser *isn't* running!), and doesn't go away when the page's tab is closed.  This is unexpected behavior for a website, and there's also no obvious way through the UI (other than an about: page) to see these and stop or uninstall them.

Handy for push notifications, but generally when a desktop user quits a *native* app, its notifications stop.  When they close a web app, however, they will continue to receive these notifications, with no obvious way to turn them off.

Service workers represent a new pattern that users may be unfamiliar with (I know I was) which may make it harder for them them to know what is running on their machine.  I propose:

a) explicitly prompting for permission from the user every time a website wants to install a service worker (separately from the "allow notifications" privilege)

b) having a visible representation in the browser toolbar indicating background activity, where clicking on it shows a dropdown of everything that's allowed to run and makes it easy to revoke permission for each.

MacOS already requires the user to allow apps to run in the background and makes it easy to revoke those permissions.  Why should firefox be *less* transparent about what's being allowed to run in the background than the operating system itself?  Moreover, surfacing this so that users are aware is both a visible demonstration that the Firefox project cares about their privacy and control over their machines, *and* would differentiate Firefox from other browsers that continue to make this invisible.

[luis123456789]

Service workers are severely hidden in current Firefox versions. I agree that their presence, configuration and elimination needs to be more visible - at the moment all we have is about:serviceworkers and just about the only thing it allows one to do is to eliminate, not to inspect.

Expanding upon @ptramsey 's suggestion, I support both request, and I think furthermore the following is needed, in relative order of preference / relevance:

• Permission to install a service worker must be a Site Preference (or more granular).
• Data cleanup dialogs (cookies, history, etc) must also include an option to either unregister/delete service workers.
• Information about an installed service worker, or a rejected permission request to install one, must be available on Site Permissions / Safety Shield Icon.
• A feature must be available to inspect and export all data and code that an installed service worker contains.