Link Previews SUMO Article (MacOS)
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: laustin, Assigned: dgalindo)
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)
Choose one below and delete others. [REQUIRED]
Firefox for Desktop (MacOS)
Select the type of request.
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.
Starting in Firefox version 142, you can preview links to learn more about a webpage before you open it.
##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
The feature will be production ready in 142.
Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]
This feature will be gradually rolled out to English locales (EN-US, EN-CA, EN-GB, EN-AU).
Please indicate if this is an on- or off-train release [REQUIRED]
This feature will be disabled by default in Firefox 142, and enabled remotely in a gradual rollout via Nimbus.
What is the anticipated release date? [REQUIRED]
August 19, 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]
No
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
Jira Issue - https://mozilla-hub.atlassian.net/browse/FIDE-2263
Bugzilla Meta - https://bugzilla.mozilla.org/show_bug.cgi?id=1943389
Labs Blog Post - https://blog.mozilla.org/en/firefox/firefox-ai/ai-link-previews-firefox/
SUMO article draft - https://docs.google.com/document/d/15SyjIKbAbyJqP4A_uB-foYyGQz1BkSbhQoPdPT3MSUo/edit?usp=sharing
Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
https://www.figma.com/design/49iKeFHi6oITxtvnG7d9Rc/Link-Previews?node-id=10553-68523&m=dev
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
Enable the feature in about:config by setting the following settings to true:
browser.ml.linkPreview.enabled
browser.ml.linkPreview.longPress
This should trigger the onboarding process. Onboarding is triggered by hovering over a web link with your cursor in the browser after enabling the feature. It has two steps:
- Introduction - press "See a preview", advance to consent and preview generation.
- Consent - press "Continue", download local model, view generative key points.
Key points are suppressed for sensitive content, for paywalled articles, or for content that is not supported by reader mode.
Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
[REQUIRED]**
Legal review - aroybal@mozilla.com
Hi Loren! We (SUMO) typically need 2 weeks prior to release for content creation. As this was submitted 1 week before release, we will not be able to complete request by 142 release and get a legal review. Additionally we do not typically create content that uses about:config as it has the potential to create unfavorable experiences for users when an update is released. As this feature is not fully released, can we postpone the content until its full release when about:config won't be necessary to activate.
Thanks - makes sense. We will proceed with the staged rollout in 142, with the expectation that the feature will be fully live/enabled by default in 143.
That works! I'm gonna get this onto our 143 roadmap. When you have the live information (how to enable/disable, etc) can you update this bug and we can use it to get the content up for 143? We can leave the information request on the bug until you update it.
Description
•