Closed Bug 1968772 Opened 1 year ago Closed 1 year ago

Updates for extensions button hiding changes (win) [Firefox V140]

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dotproto, Assigned: ffloare)

References

Details

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

Yes

Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each) [REQUIRED]

Firefox for Desktop (Windows)

Select the type of request.

Choose one or more below and delete others. [REQUIRED]

KB content update

Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]

  1. Users can now hide the extensions menu in the toolbar.
  2. The “Add-ons and themes” entry in the app menu has been renamed to “Extensions and themes”. (This affects several articles).
  3. When the extensions menu is hidden, the “Extensions and themes” app menu entry changes to “Extensions”.

All together these changes necessitate updates to several articles related to extensions in SUMO.

Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production release (140).

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

These changes are not region-specific and are implemented behind a hidden pref: extensions.unifiedExtensions.button.customizable

Please indicate if this is an on- or off-train release [REQUIRED]

On-train release.

What is the anticipated release date? [REQUIRED]

June 24 , 2025

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

No.

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Yes. The supported set of languages for each of the articles that will receive updates.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://bugzilla.mozilla.org/show_bug.cgi?id=1964857
https://mozilla-hub.atlassian.net/browse/WEBEXT-2250
https://mozilla-hub.atlassian.net/browse/ADDONSOPS-974

A video can be found at https://bugzilla.mozilla.org/attachment.cgi?id=9490665

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

I’m not aware of any.

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Use Nightly for testing.

  1. Open the app menu and observe that it contains an entry named “Extensions and themes”.
  2. Install Firefox Multi-Account Containers (https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/). The extension’s action button will automatically be added to the toolbar.
  3. Right click the Extensions Button in the toolbar and select “Remove from Toolbar”. Observe that the app menu is highlighted and a popup notifies the user that the extensions menu has “Moved to menu”.
  4. Open the app menu and observe that the “Extensions and themes” entry has been replaced by “Extensions”.
  5. Select the ”Extensions” entry in the app menu. Observe that the extensions menu temporarily appears in the toolbar in its open state.

Users can restore the Extensions Button by right clicking on the button and selecting “Always show in Toolbar”. Users can make the Extensions Button visible again by either entering Customize Toolbar mode or by selecting the “Extensions” entry from the App Menu (step 5 above).

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

:robwu

Assignee: nobody → mcacciapaglia

Articles to modify:

Main Extensions Button article

Current subsection at https://support.mozilla.org/en-US/kb/extensions-button#w_can-i-remove-the-extensions-button-from-the-toolbar-or-customize-its-location

Can I remove the extensions button from the toolbar or customize its location?
It is not possible to remove the extensions button from the toolbar. This is by design. The extensions button is now the primary user interface and allows access to per-site permissions for MV3 extensions. You can customize its location by moving it to a different position on the navigation toolbar.

The button can be removed. This should be changed. Here is an example of the message (please rephrase as needed, I am not a native speaker).

The extensions button can be removed by right-clicking the button and choosing the "Remove from toolbar" context menu item. The button will temporarily re-appear when extension-related panels are shown. You can customize its location by moving it to a different position on the navigation toolbar. When the button is hidden, its functionality can be accessed from the "Extensions" item in the application menu. To restore the button, right-click the extensions button and toggle the "Always Show in Toolbar" menu item.

Any article mentioning "Add-ons and themes" menu item

To find all articles, search for "themes", filtered by "Help Articles Only" at https://support.mozilla.org/en-US/products/firefox#search
and then Ctrl+F to find "Add-ons and themes" (may appear multiple times in one page!).
Here are examples from the first two result pages:

Change "Add-ons and themes" to "Extensions and themes". The menu item should reflect the actual localized version of the appmenuitem-extensions-and-themes string as defined at browser/locales/en-US/browser/appmenu.ftl (results in l10n repo: https://searchfox.org/l10n/search?q=appmenuitem-extensions-and-themes&path=&case=true&regexp=false)

Clarifications to the initial answers in the form:

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]
These changes are not region-specific and are implemented behind a hidden pref: extensions.unifiedExtensions.button.customizable

That pref is not relevant, and will be removed in bug 1967773.

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
I’m not aware of any.

The launch bug at bug 1964857 links to the several dependencies that include PRD and Figma links. Not linked to that bug, but still executed as part of the project is bug 1948261.
A video recording of the full feature walk-through is shown at https://bugzilla.mozilla.org/show_bug.cgi?id=1964857#c5.

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Use Nightly for testing.

Nightly is not strictly required; 140 is currently on Beta. And in 4 weeks it will be on release.

See Also: → 1964857, 1948261
See Also: → 1968774
See Also: → 1968775

Dayana, here is the Asana: https://app.asana.com/1/90589597529/project/1203460865189761/task/1210451203441639

Flags: needinfo?(dgaleano)
Assignee: mcacciapaglia → ffloare
Flags: needinfo?(dgaleano)
Duplicate of this bug: 1968774
Duplicate of this bug: 1968775
Status: NEW → ASSIGNED

So far, following the instructions provided by Rob, I've managed to find these KBs:

I'm working on this Bug this week, so I should have it ready to go by Friday.

You can review a draft here. Let me know if you have any suggestions.

Flags: needinfo?(svincent)
Flags: needinfo?(rob)
Flags: needinfo?(dgaleano)

I cannot view the doc, can you open up its access?

(In reply to Rob Wu [:robwu] from comment #7)

I cannot view the doc, can you open up its access?

Sure, I gave you access.

Flags: needinfo?(rob)

Thanks. The proposed changes look good. There was one minor inaccuracy ("Remove from Toolbar" should be with capital T; that mistake is on me, from comment 1). From my POV, you can proceed with making the changes as proposed.

I also added the following remark to the section about updating "Add-ons and themes":

Be very careful! There is another "Add-ons and Themes" menu item (in the Tools menu). This should be changed too, but to "Extensions and Themes" (capital T). I don't expect many articles pointing to the Tools menu item (maybe a handful at most), but it is good to be aware of it (and change it at the same time).

The strings are defined here:

Flags: needinfo?(svincent)

(In reply to Flavius Floare from comment #6)

You can review a draft here. Let me know if you have any suggestions.

The Google Doc is "Access Denied" for me, with no way to request access. In any case, the https://support.mozilla.org/en-US/kb/extensions-button#w_can-i-remove-the-extensions-button-from-the-toolbar-or-customize-its-location section's new content should be marked {for fx140} and the old content should be {for not fx140}, since we still support earlier versions, including Firefox 139, 128esr and 115esr.

Templates related to add-ons should be updated, since they're used by many articles (lots easier than updating all the articles that use the template!) I found this one: Template:Open Add-ons (See what links here for articles that use that template.)

I submitted a revision to update Template:Open Add-ons for fx140. See https://support.mozilla.org/en-US/kb/templateopen-add-ons/history

(In reply to Alice Wyman from comment #11)

Templates related to add-ons should be updated, since they're used by many articles (lots easier than updating all the articles that use the template!) I found this one: Template:Open Add-ons (See what links here for articles that use that template.)

I submitted a revision to update Template:Open Add-ons for fx140. See https://support.mozilla.org/en-US/kb/templateopen-add-ons/history

Thank you, Alice! Greatly appreciated. Your revision of the template will go live on 6/24, as per the bug's release time.

You're welcome. I also have a revision pending review to update Template:openextensions See: https://support.mozilla.org/en-US/kb/templateopenextensions/history

Template revisions could be approved now, since the changes I made use {for not fx140} and {for fx140} markup. One issue, though. I seem to remember that template changes may take some time to take effect within individual articles, unless some other article edit (or an "empty edit) is made that "activates" the change. I might be wrong, though. You could ask one of the SUMO engineers to check into it.

(In reply to Alice Wyman from comment #13)

You're welcome. I also have a revision pending review to update Template:openextensions See: https://support.mozilla.org/en-US/kb/templateopenextensions/history

Template revisions could be approved now, since the changes I made use {for not fx140} and {for fx140} markup. One issue, though. I seem to remember that template changes may take some time to take effect within individual articles, unless some other article edit (or an "empty edit) is made that "activates" the change. I might be wrong, though. You could ask one of the SUMO engineers to check into it.

I see. I'll review and approve the revisions to the templates by the end of this week. I'll now close this bug.

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

The update to Template:Open Add-ons was approved and the change for fx140 is displayed with no issue here, https://support.mozilla.org/en-US/kb/enable-drm#w_disable-the-google-widevine-cdm-without-uninstalling (the article itself was never updated). So, it looks like I was wrong in comment 13 that template changes may take some time to take effect.

(from comment #1)

Articles to modify:
<snip>
Here are examples from the first two result pages:

I reviewed the above articles and this one:

I edited the above articles that had unneeded revisions approved, since changes to Template:openextensions and Template:Open Add-ons for fx140 were approved as ready for localization. I submitted new revisions to save work for localizers. Flavius, can you review?

Flags: needinfo?(ffloare)

(In reply to Alice Wyman from comment #16)

(from comment #1)

Articles to modify:
<snip>
Here are examples from the first two result pages:

I reviewed the above articles and this one:

I edited the above articles that had unneeded revisions approved, since changes to Template:openextensions and Template:Open Add-ons for fx140 were approved as ready for localization. I submitted new revisions to save work for localizers. Flavius, can you review?

Hi, Alice. Thank you! Yes, I'll review them ASAP.

Flags: needinfo?(ffloare)
Flags: needinfo?(dgaleano)
You need to log in before you can comment on or make changes to this bug.