11–20 of 62 posts
I would really like Firefox to implement granular permissions per extension. So, if I can choose to not give this extension permission to talk to external programs. And hopefully the extension authors wrote it in a way that it degrades gracefully.
It's possible to benefit from containers without using the extension: https://support.mozilla.org/en-US/kb/containers#w_for-advanced-users
What functionality / convenience are you losing by doing so?
It's possible to benefit from containers without using the extension: https://support.mozilla.org/en-US/kb/containers#w_for-advanced-users
I would really like Firefox to implement granular permissions per extension. So, if I can choose to not give this extension permission to talk to external programs. And hopefully the extension authors wrote it in a way that it degrades gracefully.
It's possible to benefit from containers without using the extension: https://support.mozilla.org/en-US/kb/containers#w_for-advanced-users
I checked that page, and I don't see how to enable this natively. This page just seems to point people to install the add-on.
The tl;dr is:
> you can set privacy.userContext.enabled to true and privacy.userContext.ui.enabled to true in about:config.
Annoying change. Saw it yesterday and did not dare to accept. Good it comes up on HN, I might have forgotten. I have never looked into extensions. Could I just repackage it without requesting the additional privilege? Well, if the code called it unconditionally even if I don't really need it the extension would stop working.
It's possible to benefit from containers without using the extension: https://support.mozilla.org/en-US/kb/containers#w_for-advanced-users
What functionality / convenience are you losing by doing so?
Firefox's multi-account container extension has no special access, beyond usual extension permissions.
I wish they fixed the long standing, annoying sync bug that makes Firefox download 7000+ containers every once in a while. Some of us hosed our sync accounts in one way or another (through the container duplication bug in m-a-c itself [1] or the temporary containers extension [2]) and it's impossible to recover - once you reach the storage quota on the sync server, the sync server refuses all write operations and del…
I would really like Firefox to implement granular permissions per extension. So, if I can choose to not give this extension permission to talk to external programs. And hopefully the extension authors wrote it in a way that it degrades gracefully.
Bookmark access for the container extension is optional and there is a toggle button for it; for some reason, this one was added to the "Required permissions for core functionality" list which can not be modified.
I think these permissions cannot be optional: https://extensionworkshop.com/documentation/develop/request-...
(Not sure though, I haven't worked with optional permissions for my extensions yet.)