Closed Bug 2071609 Opened 1 month ago Closed 1 month ago

Update "How do I report a broken site in Firefox desktop?" SUMO KB article with new app menu "Help and Report" instructions (Firefox v155)

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: alice.wyman, Assigned: alice.wyman)

References

(
URL
)

Details

Attachments

(5 files)

Fx155menu-ReportBrokenSite.png
23.68 KB, image/png
Details
Fx155menu-HelpAndReport.png
95.84 KB, image/png
Details
Fx155ReportBrokenSiteSubmenu.png
68.61 KB, image/png
Details
Fx155ReportBrokenSite-SendReport.png
61.02 KB, image/png
Details
Fx155ReportBrokenSiteSentReport-Okay.png
30.80 KB, image/png
Details

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

**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **
N/A

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

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

Note: If yes, ensure ‘Advanced Fields’ are visible by selecting ‘Show Advanced Field’ at the top right, then scroll to ‘Security’ and check ‘Confidential Mozilla Employee Bug (non-security)’.
No

Attention: Any content not marked as confidential will be accessible to both NDAd and non-NDAd contributors with a Bugzilla account. Drafts for non-confidential content will also follow the same access policy, being open to comments for anyone with the link. Non-confidential Bugzillas can benefit from contributions by community contributors, while confidential Bugzillas will be handled exclusively by staff.

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

Choose one below and delete others. [REQUIRED]
Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)

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]

The Firefox menu items for "Help" and "Report Broken Site" have been combined into a single "Help and Report" menu, which includes a "Report Broken Site" submenu. The How do I report a broken site in Firefox desktop? article and others that refer to these menu items will need an update. I would rather have staff handle this, since I was unable to find a related bugzilla report about the change and it may be a bug that I can't access for whatever reason. See https://support.mozilla.org/en-US/kb/report-breakage-due-blocking/history and the May 2026 revision 328039 Comment: Major update to one of the sections. See Bug 2034092. (Bug 2034092 is still Access Denied" for me. So is Bug 1981534 which is mentioned in the comment for the previous October 2025 revision 309852.

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

**Note: Specify if the user-facing changes mentioned above are final, experimental, or in beta. This information is crucial for determining the appropriate support and documentation level needed. Please note that SUMO KB articles only support the production version for Firefox.
Firefox 155 release

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

**Note: Please confirm if these features or changes are limited to specific geographic regions and if they will be implemented gradually. Knowing this helps us tailor our documentation and support resources appropriately.
?

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

**Note: If applicable, add the product version number to the end of the Summary field using the format: Summary [Product V123]. If this is an off-train release, please use the format: Summary [Product off-train].
?

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
Firefox 155 is already released

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

Note: If you don’t let us know if this date changes, it will be published on this date
N/A

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

Note: A minimum of 10 days is required for translation requests.
?

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

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

Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'

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

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

Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
Should be reviewed by Mozilla staff

Screenshot (Windows 11 en-US)

Screenshot: Firefox 155 main menu with "Help and Report" menu item (Windows 11 en-US)

Firefox 155 menu > Help and Report > Report Broken Site > Report broken site submenu with website URL and reporting options. The "Learn more" link at the bottom takes me to the How do I report a broken site in Firefox desktop? article

Screenshot of Firefox 155 "Send report" dialog when one of the Report broken site submenu options is selected

Summary: Update SUMO KB "How do I report a broken site in Firefox desktop?" (desktop v155) → Update "How do I report a broken site in Firefox desktop?" SUMO KB article with new app menu "Help and Report" instructions (Firefox v155)

In addition to updating the "How do I report a broken site in Firefox desktop?" article, the Enhanced Tracking Protection in Firefox for desktop article's "Report a broken site" section will also need an update for fx155 since it includes the same outdated instructions.

(from comment #3)

Created attachment 9641544 [details]
Fx155ReportBrokenSiteSubmenu.png

Firefox 155 menu > Help and Report > Report Broken Site > Report broken site submenu with website URL and reporting options.

Even though you still accessed "Report broken site" from the main app menu in Firefox 154 and earlier, did the reporting options and other UX design elements change before fx155? See bug 2028605 (fixed in fx152) and the follow-up bug 2040437. See bug 2046937 (fixed in fx154) regarding the "something else" option.

See Also: → 2028605

Good catch, Alice. I was informed that this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=2023762. I checked the figma file from there and can confirm that this is something we introduced only in 155.

Would you like to work on the actual KB update? I know you've been trying to reduce your screen time, so let me know if you prefer not to.

Flags: needinfo?(alice.wyman)

(In reply to Kelimutu [:kiki] from comment #7)

Good catch, Alice. I was informed that this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=2023762. I checked the figma file from there and can confirm that this is something we introduced only in 155.

Would you like to work on the actual KB update? I know you've been trying to reduce your screen time, so let me know if you prefer not to.

Thanks, Kiki. I see that bug 2023762 was fixed in firefox 155 and that bug 2023762 comment 2 says, ... Report Broken Site moves into Help and Report section (FKA Help).

I checked in Firefox 154 on macOS and the Firefox app ("hamburger") main menu still includes separate "Help" and "Report Broken Site" menu items. However, when you open the "Report Broken Site" menu, the UX design elements are the same as fx155: "What's not working" and the list of reporting menu items, including the last "Something else" option shown in the Fx155ReportBrokenSiteSubmenu.png image I attached in comment 3. See bug 2046937 (fixed in fx154) regarding the "Something else" option.

I'm going to assume that the UX design change took place in Firefox 152, as per bug 2028605 (fixed in fx152) and the follow-up bug 2040437. In that case (can you confirm?) you can assign the bug to me to fix both the "How do I report a broken site in Firefox desktop?" article as well as the Enhanced Tracking Protection in Firefox for desktop article's "Report a broken site" section.

Flags: needinfo?(alice.wyman)

I submitted revisions for the Firefox "Help and Report" menu option change but updates are still needed for the UX redesign (bug 2028605). See:

Assignee: nobody → alice.wyman
Status: NEW → ASSIGNED

Firefox 155 Report broken site - Sent report success message with Okay button (Windows 11 en-US)

(from comment #10)

I submitted new revisions for the UX redesign in fx152 (bug 2028605). See:

Donna Kelly approved my fx155 and fx152 revisions to both articles so I'll resolve this bug as fixed

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

I submitted revisions to all of the articles and templates that include accessing the "Help" menu from the main menu ("hamburger" button), to change "Help" to "Help and Report" for fx155 and above. See:
https://support.mozilla.org/en-US/kb/revisions?locale=en-US&users=AliceWyman&start=2026-09-20&end=2026-09-21

(from comment #13)

I submitted revisions to all of the articles and templates that include accessing the "Help" menu from the main menu ("hamburger" button), to change "Help" to "Help and Report" for fx155 and above. See:
https://support.mozilla.org/en-US/kb/revisions?locale=en-US&users=AliceWyman&start=2026-09-20&end=2026-09-21

I missed one. I submitted a revision that needs review: https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems/history

(from comment #14)

(from comment #13)

I submitted revisions to all of the articles and templates that include accessing the "Help" menu from the main menu ("hamburger" button), to change "Help" to "Help and Report" for fx155 and above. See:
https://support.mozilla.org/en-US/kb/revisions?locale=en-US&users=AliceWyman&start=2026-09-20&end=2026-09-21

I missed one. I submitted a revision that needs review: https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems/history

Another missed article. Pending revision: https://support.mozilla.org/en-US/kb/update-failed-error-message-when-updating/history
...and here's one that Michele (michro) caught: https://support.mozilla.org/en-US/kb/use-troubleshooting-information-page-fix-firefox/history (I approved it.

(EDIT) These revisions to change "Help" to "Help and Report" for fx155 and above are still pending review:

^(EDIT) All are now approved.

I missed another one and submitted a revision that's pending:

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: