This feature has evolved considerably in pre-release testing and is much more useful than before, but still there are still unhappy early adopters posting on Reddit this afternoon. For example:
Our KB article does not mention that the feature can be disabled using the (temporary?) preference extensions.unifiedExtensions.enabled. After a restart, some of the extension items migrate to the legacy overflow menu button and some can no longer be managed from the toolbar:
This is going to become much more significant when Manifest v3 extensions become more available, since being able to monitor and manage site permissions is very important for those extensions.
Firefox 109 debuts the Extensions button on Release, and there is a new article: [[Manage your extensions using the extensions button in the toolbar]]
This feature has evolved considerably in pre-release testing and is much more useful than before, but still there are still unhappy early adopters posting on Reddit this afternoon. For example:
* [https://www.reddit.com/r/firefox/comments/10dcjre/new_unified_extensions_button_worst_mozilla_idea/ New Unified Extensions Button, worst mozilla idea of the decade]
* [https://www.reddit.com/r/firefox/comments/10do6a2/firefox_109_why_oh_why/ Firefox 109 . . . Why, Oh Why?] - also mentioning breakage in userChrome.css rules
Our KB article does not mention that the feature can be disabled using the (temporary?) preference '''extensions.unifiedExtensions.enabled'''. After a restart, some of the extension items migrate to the legacy overflow menu button and some can no longer be managed from the toolbar:
[[Image:Extensions button vs. Overflow - Firefox 109]]
This is going to become much more significant when Manifest v3 extensions become more available, since being able to monitor and manage site permissions is very important for those extensions.
userChrome.css hacks are not officially supported, so these breaking is not something we can manage.
That about:config pref is due to be removed in the near future, so flipping it raises an unrealistic expectation of a permanent fix. I also understand that it will break MV3 add-ons - another good reason to leave it well alone.
userChrome.css hacks are not officially supported, so these breaking is not something we can manage.
That about:config pref is due to be removed in the near future, so flipping it raises an unrealistic expectation of a permanent fix. I also understand that it will break MV3 add-ons - another good reason to leave it well alone.
This new menu is part of MV3 and disabling/removing it will prevent the user to manage their addons. The current implementation gives the same abilities as what we had with addons in the overflow menu so there's no ground in users arguing that things are still missing. The only difference being that addons have their own menu now.
If this breaks someone userChrome.css, that's on them to update their script since the moment they decided to use one they "avoided their warranty" by using an unsupported feature. They can always use ESR if they want to avoid frequent breakages.
This new menu is part of MV3 and disabling/removing it will prevent the user to manage their addons. The current implementation gives the same abilities as what we had with addons in the overflow menu so there's no ground in users arguing that things are still missing. The only difference being that addons have their own menu now.
If this breaks someone userChrome.css, that's on them to update their script since the moment they decided to use one they "avoided their warranty" by using an unsupported feature. They can always use ESR if they want to avoid frequent breakages.
But ESR only buys them a little time. With the move to MV3, it is likely that this year's ESR will not have that pref to give add-on developers moving their code to MV3 certainty around what users have.
The sooner users move to MV3, the better for them to continue to access add-ons they wish to continue to use.
But ESR only buys them a little time. With the move to MV3, it is likely that this year's ESR will not have that pref to give add-on developers moving their code to MV3 certainty around what users have.
The sooner users move to MV3, the better for them to continue to access add-ons they wish to continue to use.
For my own add-ons, after re-reading the migration documentation several times, I'm sticking with MV2 as long as possible. I don't think I'm the only one who dreads the rewrite. (Although maybe in a few months, ChatGPT can do it for me.)
MV3 will become important eventually.
For my own add-ons, after re-reading the migration documentation several times, I'm sticking with MV2 as long as possible. I don't think I'm the only one who dreads the rewrite. (Although maybe in a few months, ChatGPT can do it for me.)
I have got most of mine ready to be republished (just got four to do). This duel running of MV2 and MV3 is really useful as it means we can release updates to our add-ons without impacting users based on the user population usage of Fx versions in the stats for our add-ons.
It really is in users best interests to not hide the new toolbar icon.
I have got most of mine ready to be republished (just got four to do). This duel running of MV2 and MV3 is really useful as it means we can release updates to our add-ons without impacting users based on the user population usage of Fx versions in the stats for our add-ons.
It really is in users best interests to not hide the new toolbar icon.
''Paul [[#post-84907|said]]''
<blockquote>
It really is in users best interests to not hide the new toolbar icon.
</blockquote>
Can we add something about not hiding the new Extensions button to the KB article [[Manage your extensions using the extensions button in the toolbar]] '''Common questions''' section? See discussion:
<s>https://support.mozilla.org/en-US/kb/unified-extensions/discuss/11118#post-24486</s>
<sub>New link (renamed article): https://support.mozilla.org/en-US/kb/extensions-button/discuss/11118#post-24486</sub>
I think it would be appropriate (Common questions section).
''AliceWyman [[#post-84913|ha detto]]''
<blockquote>
''Paul [[#post-84907|said]]''
<blockquote>
It really is in users best interests to not hide the new toolbar icon.
</blockquote>
Can we add something about not hiding the new Extensions button to the KB article [[Manage your extensions using the extensions button in the toolbar]] '''Common questions''' section? See discussion:
https://support.mozilla.org/en-US/kb/unified-extensions/discuss/11118#post-24486
</blockquote> I think it would be appropriate (Common questions section).
I made a small edit just now and then approved my revision.
I made a revision to the [[Manage your extensions using the extensions button in the toolbar]] article that's pending review, to add the following to the '''Common questions''' section:
<nowiki>
==Can I remove the extensions button from the toolbar or customize its location?==
No, it is currently not possible to remove this button or change its location. This is by design. The extensions toolbar button is now the primary user interface and allows access to per-site permissions for MV3 extensions. <!-- https://bugzilla.mozilla.org/show_bug.cgi?id=1795079 and https://bugzilla.mozilla.org/show_bug.cgi?id=1795235 -->
</nowiki>
I made a small edit just now and then approved my revision.
Hi Alice, I think it's premature to say it is "not possible to remove" as long as there is a preference for that. I think saying it is unsupported and may prevent full use of some add-ons are more accurate for the time being.
Hi Alice, I think it's premature to say it is "not possible to remove" as long as there is a preference for that. I think saying it is unsupported and may prevent full use of some add-ons are more accurate for the time being.
Hi Alice, I think it's premature to say it is "not possible to remove" as long as there is a preference for that. I think saying it is unsupported and may prevent full use of some add-ons are more accurate for the time being.
I was using the language posted in bug 1795235 comment 2 by William Durand (quote) Hi, sorry it is indeed currently not possible to remove this button, by design.
I know there's a preference to disable the feature but I didn't know if or how we should work it in. Can you make a revision? What do you think about adding something like this to the end of the new "Can I remove the extensions button ..." section?
(Modifying the related preference to disable this new feature is not supported and may prevent full use of some add-ons.)
''jscher2000 - Support Volunteer [[#post-84919|said]]''
<blockquote>
Hi Alice, I think it's premature to say it is "not possible to remove" as long as there is a preference for that. I think saying it is unsupported and may prevent full use of some add-ons are more accurate for the time being.
</blockquote>
I was using the language posted in [https://bugzilla.mozilla.org/show_bug.cgi?id=1795235#c2 bug 1795235 comment 2] by William Durand (quote) ''Hi, sorry it is indeed currently not possible to remove this button, by design.''
I know there's a preference to disable the feature but I didn't know if or how we should work it in. <s>Can you make a revision?</s> What do you think about adding something like this to the end of the new "Can I remove the extensions button ..." section?
(Modifying the related preference to disable this new feature is not supported and may prevent full use of some add-ons.)
Thanks for starting this thread. I like the new section in this article that explains why we don't support disabling the extensions button. On that note, there's also a Reddit comment posted by a staff member that explain why users can't remove or move the button.
Regarding users who may still have feedback about the extensions button, the following Mozilla Connect thread might be useful to direct if it's related:
Hey folks,
Thanks for starting this thread. I like the new section in [https://support.mozilla.org/kb/extensions-button this article] that explains why we don't support disabling the extensions button. On that note, there's also [https://www.reddit.com/r/firefox/comments/10j7ndc/comment/j5j4bnq/?utm_source=reddit&utm_medium=web2x&context=3 a Reddit comment] posted by a staff member that explain why users can't remove or move the button.
Regarding users who may still have feedback about the extensions button, the following Mozilla Connect thread might be useful to direct if it's related:
* [https://connect.mozilla.org/t5/ideas/please-let-us-move-the-new-extensions-button-into-the-overflow/idi-p/22979 Ability to move the extensions button back to the overflow menu]
* [https://connect.mozilla.org/t5/ideas/unified-add-ons-ui-improvements/idi-p/20964 Ability to customize Unified Extensions Butto (add pinning functionality)]
Also, for those interested in having the ability to reorder the list in the UEB, you can follow bug1805924.
Also, for those interested in having the ability to reorder the list in the UEB, you can follow [https://bugzilla.mozilla.org/show_bug.cgi?id=1805924 bug1805924].
Besides following Bug 1805924, there's also this workaround posted in bug 1811221 (filed for a different issue) on how to change the order of extensions in the toolbar and panel:
Peter_M Comment 2 • 2023-01-20 06:06 EST
You can change the order of your extensions once you have them pinned to the toolbar (<snip>). In order to move them around can open the hamburger menu (application menu) -> More tools -> Customise toolbar... and drag and drop the pinned extensions to set them in the order/place you'd like. If you only want to change the order inside the extensions menu (unpinned) you can then unpin them one-by-one, the last one will always go on top. (when installing them, the latest one will go on the bottom of the list)
Extensions pinned to the toolbar can be managed from the context menu. [[T:contextmenu]] the pinned extension in the toolbar to view the available options.
You can unpin an extension from the toolbar and restore it to the extensions panel by removing the check mark from the {menu Pin to Toolbar} option. Pinned extensions can also be moved to a different position on the toolbar using the {menu Customize Toolbar…} option.
Besides following [https://bugzilla.mozilla.org/show_bug.cgi?id=1805924 Bug 1805924], there's also this workaround posted in [https://bugzilla.mozilla.org/show_bug.cgi?id=1811221#c2 bug 1811221] (filed for a different issue) on how to change the order of extensions in the toolbar and panel:
;Peter_M Comment 2 • 2023-01-20 06:06 EST
;You can change the order of your extensions once you have them pinned to the toolbar (<snip>). In order to move them around can open the hamburger menu (application menu) -> More tools -> Customise toolbar... and drag and drop the pinned extensions to set them in the order/place you'd like. If you only want to change the order inside the extensions menu (unpinned) you can then unpin them one-by-one, the last one will always go on top. (when installing them, the latest one will go on the bottom of the list)
----
I also noticed that some users don't know how to remove (unpin) extension toolbar icons using the (right-click)[https://support.mozilla.org/en-US/kb/Template:contextmenu context menu], which adds them back to the extensions panel. I added a new '''Manage pinned extensions''' section to the [[Manage your extensions using the extensions button in the toolbar]] article:
----
==Manage pinned extensions==
Extensions pinned to the toolbar can be managed from the context menu. [[T:contextmenu]] the pinned extension in the toolbar to view the available options.
;[[Image:Fx109PinnedExtension-ContextMenu]]
You can unpin an extension from the toolbar and restore it to the extensions panel by removing the check mark from the {menu Pin to Toolbar} option. Pinned extensions can also be moved to a different position on the toolbar using the {menu [[Customize Firefox controls, buttons and toolbars|Customize Toolbar…]]} option.
----
I have some other edits to the article that are pending review. See https://support.mozilla.org/en-US/kb/extensions-button/history
^ Edits approved today (Jan 29, 2023)
Hi All,
The about:config preference to hide the Unified Extensions Button has been removed in Fx 111 - this is necessary to make sure that when add-ons move to MV3 that they will still work. Users who already flipped that preference will see the UEB reappear. There are plans to allow the UEB to be moved on the toolbar, but it will not be possible to hide it.
(For the record)
https://support.mozilla.org/en-US/forums/contributors/716226#post-85146 Firefox 111 for Desktop - Release Notes / Issues / Discussions
''SUMOsJR [[#post-85146|said]]''
<blockquote>
Hi All,
The about:config preference to hide the Unified Extensions Button has been removed in Fx 111 - this is necessary to make sure that when add-ons move to MV3 that they will still work. Users who already flipped that preference will see the UEB reappear. There are plans to allow the UEB to be moved on the toolbar, but it will not be possible to hide it.
</blockquote>
There is a fix in Nightly that allows users to move the button within the main toolbar (similar to the Back/Forward buttons). Unfortunately, there are no more beta releases for testing so there is reluctance of uplift it to Firefox 112.
I don't know whether anyone can speak with anyone about this so it can be prioritized; there are a lot of unhappy users and this would help the ones that click in that place out of habit because they've always had a different button there.
There is a fix in Nightly that allows users to move the button within the main toolbar (similar to the Back/Forward buttons). Unfortunately, there are no more beta releases for testing so there is reluctance of uplift it to Firefox 112.
[https://bugzilla.mozilla.org/show_bug.cgi?id=1820743#c10 1820743 - Allow to move unified extensions button on the navbar]
I don't know whether anyone can speak with anyone about this so it can be prioritized; there are a lot of unhappy users and this would help the ones that click in that place out of habit because they've always had a different button there.
https://connect.mozilla.org/t5/ideas/please-let-us-move-the-new-extensions-button-into-the-overflow/idi-p/22979 (813 votes)
