Bug 2021712 Comment 0 Edit History

Original comment by

on 2026-03-07 07:14:47 PST

## 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 **

**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)’.**

**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]

Firefox 149 Beta has new security error pages. For example, compare these media gallery images:

Test page: https://tls-v1-1.badssl.com:1011/
Fx148SecureConnectionFailed-TLS https://support.mozilla.org/en-US/gallery/image/57164
Fx149BetaSecureConnectionFailed https://support.mozilla.org/en-US/gallery/image/57135

Test page: https://pinning-test.badssl.com/
Fx148DidNotConnectPotentialSecurityIssue-pinningtest https://support.mozilla.org/en-US/gallery/image/57154
Fx149BetaWarningSecurityRisk-pinningtest https://support.mozilla.org/en-US/gallery/image/57156

Test page: https://subdomain.preloaded-hsts.badssl.com/
Fx148WarningPotentialSecurityRiskAhead-hsts https://support.mozilla.org/en-US/gallery/image/57147
Fx149BetaWarningSecurityRisk-hsts Fx149BetaWarningSecurityRisk-hsts

Test page: https://expired.badssl.com/
Fx148Warning-SecurityRiskTimeRelated https://support.mozilla.org/en-US/gallery/image/57168
Fx149BetaWarning-SecurityRiskTimeRelated https://support.mozilla.org/en-US/gallery/image/57137

I submitted a revision (see https://support.mozilla.org/en-US/kb/troubleshoot-time-errors-secure-websites/revision/321242} to this article:
- https://support.mozilla.org/en-US/kb/troubleshoot-time-errors-secure-websites

Updates to these other articles are needed:
- https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean
- https://support.mozilla.org/en-US/kb/error-codes-secure-websites
- https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/

Related discussion, with other images:
https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/discuss/14561 [Fx149] Update, new images needed

## 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.
Not sure if this is only in Beta or if it is for Fx149 release. Can the Firefox product or SUMO KB Content team verify?

## 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.
Unknown. Can the Firefox product team or SUMO KB Content team verify?

## 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 149 release date is March 24, 2026

## 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**

## 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.**
Yes, all

## 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]**

Revision 1 by

Alice Wyman

on 2026-03-07 10:56:34 PST