272650 - lock globally installed extensions automatically

Status: RESOLVED WONTFIX

(Toolkit :: Add-ons Manager, defect)

Description

[Steffen Wilberg]

When you install an extension globally by using
-install-global-extension "/path/to/extension",
any user can disable or uninstall that extension with effect to all users,
unless you use -lock-item {GUID} after the installation to prevent that.

See http://www.mozilla.org/projects/firefox/extensions/commandlineoptions.html.

Shouldn't we automatically lock extensions when installed globally?

Comment 1

[Joe Shaw]

I see this too, but I can't actually uninstall it because I don't have the
rights on the filesystem to remove/change those files.  I am able to click
"Uninstall" in the GUI, however, and Firefox tells me that it'll be uninstalled
after a restart.

Comment 2

[timeless]

locking them is the wrong thing to do. perhaps uninstall should offer to disable
instead if it can't uninstall...

Comment 3

[Steffen Wilberg]

"Disable" affects the other users as well.

The user doesn't expect to be able to uninstall or disable an extension for all
users. So when the extension manager makes offers it, he'd think it only affects
himself. He clicks uninstall, and oops, it's gone for all users (after he
restarts Firefox, and then the other users).

Comment 4

[timeless]

that's a bug :)

Comment 5

[Mike Shaver (:shaver emeritus)]

That's very much a bug.  When the bugs around global/per-user extensions settle,
I think this will be a WONTFIX: installing something globally doesn't mean that
you don't want users to be able to disable them.

Comment 6

[Joe Shaw]

Fair enough, but the Uninstall button should either be grayed out or replaced
with a Disable button.

Comment 7

[Robert Strong (they/them - no direct email)]

Current behavior is to not allow uninstall or update to extensions installed
into a read only location and the widgets are disabled. Also, if a user disables
an extension it is only disabled for the profile the user disabled it with. Is
this acceptable or is there more that needs to be done to resolve this bug?

Comment 8

[Robert Strong (they/them - no direct email)]

Resolving -> wontfix

If the current behavior as described in comment #7 needs improvement please file
a new bug