3 ms·

Some more detail about the control that the new extensions button gives users: https://blog.mozilla.org/addons/2022/11/17/unified-extensions-button-and-how-to-h

by Vinnl 4y ago

Some more detail about the control that the new extensions button gives users: https://blog.mozilla.org/addons/2022/11/17/unified-extensions-button-and-how-to-handle-permissions-in-manifest-v3/ https://blog.mozilla.org/addons/2022/11/17/unified-extension... It allows you to disable extensions only on specific sites. (And presumably, that's also the reason you need to dive into about:config to remove it: if you remove it, it's pretty hard for casual users to find out why an extension isn't working. By gating it behind about:config, people who are able to deal with that can still remove it without rendering casual users helpless. That's my personal interpretation though.)

gnicholas 4y ago
Does this allow whitelisting as well as blacklisting? Chrome has offered both for a long time, and I remember being surprised to learn that FF didn't offer either. It's a welcome change!
pentagrama 4y ago
I was checking this new extension button, I think is useful to give more light to extensions, but what I don't like it at all is that it only shows the extensions that are not present on the nav bar, not all your installed extensions. I think is confusing, it should be the list of all your extensions, and the user can pick which extension also appears more handy on the nav bar.
- Yaina 4y ago
  That was in the original spec, but had to be changed because of technical constraints in the toolbar code. Hopefully that can be addressed at some point in the near future :)