1974664 - SUMO Update for Semantic History Search

Status: VERIFIED FIXED

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

Description

[nsuresh]

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

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 experiment sizing isn't determined yet, but we're looking to change the way we rank history suggestions using Semantic history. Some documents:

• PRD: https://docs.google.com/document/d/1vIyeAYKZSp4W2fpQQGxkDvmvmrSPbCvblyDIDLb0mcc/edit?tab=t.0
• Foxfooding: https://docs.google.com/document/d/1gmCaZhMeJ-e8qCdl5m3kalcRqk68Z121S0pFE9ch8Kk/edit?tab=t.0#heading=h.rq2ueehja1cb

Even though it's for a small population, this is a highly visible change that uses AI/ ML and can affect user perception. We'd like to create a paragraph around what this is, what the impact is and mention that not everyone can see it in an existing SUMO page

##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.
This is experimental but we'd look to roll it out further if it does well. As mentioned above, this is a highly visible change using AI/ ML so we'd like to add in an exerpt about this in an existing SUMO page

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.
They are not region-specific

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].
On-train experiment targeting Fx 141

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
July 29, 2025

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
On or before will be good

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.
No

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

https://mozilla-hub.atlassian.net/browse/SSPGM-210

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]
Yes, approver would be Nive Suresh or Chris Bellini

Comment 1

[Seburo]

Sadly access to the doc is being actively declined to contributors which is both sad and unfortunate.

This looks like an experiment which we do not normally support. Are there any controls that users might need to turn this feature off?

Comment 2

[Seburo]

Got access to the doc \o/, and this one looks interesting.

Mind if I pick this one up and work with the requestor on it?

Comment 3

[JC]

Asana task created https://app.asana.com/1/90589597529/project/1203460865189761/task/1210677006309012?focus=true

Comment 4

[Kelimutu [:kiki]]

(In reply to Seburo from comment #2)

Mind if I pick this one up and work with the requestor on it?

Go for it, Paul. Please share the draft here once you finish it. I'll be happy to shepherd the publishing process here.

Comment 5

[Seburo]

Further to work on Slack, draft for Nive or Chris to approve - https://docs.google.com/document/d/12NZSYOvdnMbFWOqkJjwkxa15ZnmclIfvBh3Uk0TJ_Nc/edit?usp=sharing

Once I either of your support on this, I will then upload to Kitsune for SUMO staff to review. Once they have reviewed it, it will be passed to SUMO L10n to localise.

Comment 6

[Chris Bellini (:cbellini)]

:Seburo, this looks good to me!

Comment 7

[Seburo]

Ready for review - https://support.mozilla.org/en-US/kb/search-firefox-address-bar/history#preview

Comment 8

[Kelimutu [:kiki]]

Dayani, can you review the above?

Comment 9

[Dayani Galindo]

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

Dayani, can you review the above?

Reviewed and approved

Comment 10

[Kelimutu [:kiki]]

Thanks for sharing the campaign link, Alice. Just to clarify, the campaign is a different thing from this experiment. The campaign is for 142 Beta, while this experiment is targeting 141 Release.