1925368 - SUMO update Address Bar of https://support.mozilla.org/en-US/kb/how-do-i-tell-if-my-connection-is-secure [V136]

Status: RESOLVED FIXED

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

Description

[Chris Bellini (:cbellini)]

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/ new content

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]

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

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

All regions.

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

On-train in Fx 136 Release

What is the anticipated release date? [REQUIRED]

March 4

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]

All supported regions.

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

https://bugzilla.mozilla.org/show_bug.cgi?id=1891857

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]

Comment 1

[Lucas Siebert]

Task link in the Asana Content Roadmap: https://app.asana.com/0/1203460865189761/1208563180480582/f

Comment 2

[Alice Wyman]

Lucas,I don't have access to the task link you posted or to https://mozilla-hub.atlassian.net/browse/SNG-1869 but bug 1850491 indicates that https:// will now be hidden in the address bar and http:// pages will have a Not Secure label. In that case, the https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox article (and probably other KB articles) will also need an update.
Related discussion: https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox/discuss/12510

Comment 3

[Alice Wyman]

Lucas, you approved my October 25, 2024 revision to the https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox/ where I added the following {for not fx134} markup to the intro:
A secure webpage will have {for not fx134}an address that begins with ''https://'' and {/for}a lock icon [[Image:Fx89Padlock]] in the address bar.

When I view this page in Firefox 132 (Windows 10) and I set "Customize this article" to Version 134, I see the same content for Firefox 134 as I do for Firefox 133 and below:
A secure webpage will have an address that begins with https:// and a lock icon Fx89Padlock in the address bar.
... and the URL is shown as https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox#firefox:win10:fx133

When I view the article Firefox 134 Nightly, the "Customize this article" version picker shows Version 132 and when I change the version picker to Version 134, #firefox:win10:fx133 is also shown at the end of the URL. (The same happens with other KB articles.)

Was there an error when Version 134 was added to the version picker KB software or is this a temporary glitch?

Comment 4

[Lucas Siebert]

(In reply to Alice Wyman from comment #3)
Hey Alice! I think there’s a glitch with the version picker. On my end, using Firefox Beta 133, it defaults to V134 whenever I access https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox. I double-checked the version picker settings, and it’s set to default to V132. This doesn’t quite match what you described but shows that something’s off with it.
Could you please open a bug with the platform team and send me the link? I’ll bring it up in the next team meeting. Thanks so much!

Comment 5

[Alice Wyman]

(In reply to Lucas Siebert from comment #4)

(In reply to Alice Wyman from comment #3)
Hey Alice! I think there’s a glitch with the version picker. On my end, using Firefox Beta 133, it defaults to V134 whenever I access https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox. I double-checked the version picker settings, and it’s set to default to V132. This doesn’t quite match what you described but shows that something’s off with it.
Could you please open a bug with the platform team and send me the link? I’ll bring it up in the next team meeting. Thanks so much!

Bug 1930918 opened.

Comment 6

[Chris Bellini (:cbellini)]

We've updated the target to Fx 135.

Comment 7

[Alice Wyman]

Attachment: Fx135AddressBarHTTPS.png

Firefox 135beta still shows https in the address bar. Has this been moved to fx136?

Comment 8

[Chris Bellini (:cbellini)]

Thanks for catching this, Alice! Yes, this is now targeting Fx 136.

Comment 9

[Alice Wyman]

Firefox 136 beta still shows https in the address bar. Has this been moved to fx137?

Comment 10

[Dayana]

Hey Jo! Could you check if this request is still valid? Should we re-assign?

Comment 11

[Jo Thomas]

@dayana - Dayani already has a draft for this and I think it's ready for publish

Comment 12

[Dayana]

(In reply to Jo Thomas from comment #11)

@dayana - Dayani already has a draft for this and I think it's ready for publish

Reassigned this ticket to Dayani so she can add updates here!

Comment 13

[Ryan VanderMeulen [:RyanVM]]

Is there more to do here?

Comment 14

[Alice Wyman]

See https://support.mozilla.org/en-US/kb/how-do-i-tell-if-my-connection-is-secure/history (update pending review)

Comment 15

[Dayani Galindo]

(In reply to Alice Wyman from comment #14)

See https://support.mozilla.org/en-US/kb/how-do-i-tell-if-my-connection-is-secure/history (update pending review)

Reviewed, thanks.