In-Product Link for Trending Searches on New Tab [Firefox Desktop 140]
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: jimthomas, Assigned: dgalindo)
References
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 **
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
Select the type of request.
Choose one or more below and delete others. [REQUIRED]
In-product link request
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]
We will be running an experiment with our existing trending search results feature on the new tab page. We need a new in-product link for users to "Learn more" about how trending searches work on new tab.
##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.
Feature is in release, the new tab integration is experimental
See: https://support.mozilla.org/en-US/kb/use-google-trending-search-firefox-address-bar?as=u&utm_source=inproduct
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.
No
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, Fx140
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
June 24
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
No
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
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
https://mozilla-hub.atlassian.net/browse/HNT-450
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'
https://www.figma.com/design/xUoOLxuxVbgWWw2LbXfiFU/Search-%2F-HNT?node-id=477-3607&p=f&t=nHFxBgaJOzSjc9VJ-0
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
Will add the pref when available
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]
No
Hey Jo! Could you validate and add to the Asana Content Roadmap?
(In reply to Jim T from comment #3)
Hi there - are there any updates on this request?
Hi Jim! We apologize for not having updates since this was submitted. We're currently working on getting our technical writer access to the Kitsune dashboard so she can create the in-product link.
Comment 5•11 months ago
|
||
(In reply to Jim T from comment #3)
Hi there - are there any updates on this request?
Hi Jim, In addition to what Dayana noted in comment 4, this request is listed for Firefox V140 landing June 24th from what I can see.
Just so you are aware, we normally do not work on content request like this, this far out from the identified release date. Can you help me understand the urgency behind your requests for an update?
Because the code is landing on train, we need a placeholder URL by the time the nightly cycle closes (i.e. May 22 for Fx140). We don't need the actual content, just a link that we can put in the code which won't change. I assume any links landing in Firefox would have the same timeline, so let me know if there's a different way I need to flag that.
Thanks!
Comment 7•10 months ago
|
||
Here is the in-product link: https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/trending-searches-new-tab
Thanks, Jim!
(In reply to Jim T from comment #6)
Because the code is landing on train, we need a placeholder URL by the time the nightly cycle closes (i.e. May 22 for Fx140). We don't need the actual content, just a link that we can put in the code which won't change. I assume any links landing in Firefox would have the same timeline, so let me know if there's a different way I need to flag that.
Thanks!
Hey Jim, the place holder has been created as requested. We're going to close the ticket but, please let us know if you need anything else!
Comment 9•10 months ago
|
||
I have verified this task using the latest Firefox Nightly 141.0a1 (Build ID: 20250612214230) build on Windows 10 x64, macOS 14.7.1, and Ubuntu 24.04.1.
- After clicking the “Learn more” contextual menu option, a SUMO page opens in the tab stating a 404 “Page not found” error, and its URL is: “https://support.mozilla.org/%LOCALE%/kb/trending-searches-new-tab?as=u&utm_source=inproduct”.
Description
•