Please write an overview of Smart Tab Groups
Categories
(support.mozilla.org :: Knowledge Base Content, task, P1)
Tracking
(firefox138+ fixed)
People
(Reporter: ssmagula, Assigned: dgalindo, NeedInfo)
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 **
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)’.
NOT RESTRICTED
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) YES
Firefox for Desktop (macOS) YES
Firefox for Desktop (Linux) YES
Select the type of request.
Choose one or more below and delete others. [REQUIRED]
KB content update/ new content
New Content Needed
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]
EXPERIMENTAL
**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.
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.
en-US ONLY
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
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
Release 138, 29 April 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
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.
Not now
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
See: https://docs.google.com/document/d/11Jz-U7EIu3mqR2v4Zykjoe_FkFVFgFHOJKXr3KbvLL8/edit?usp=sharing
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'
See doc above for link to mockups. Talk to Laura Lopez and Amy Lee for questions.
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
Self-enroll in the forthcoming experiment
Create a tab group
Click the "Suggest..." button
Opt into the Smart Tab Groups feature
See the suggested group title and the suggested similar tabs to add to the group
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]
Stefan Smagula
| Reporter | ||
Comment 1•1 year ago
|
||
Here are some people to talk to about this article:
Rolf Rando, Tech Lead
Amy Lee, UX Lead
Laura Lopez, Content Lead
Hey Jo! Could you add this to the Asana Content Roadmap under the V138 release?
Comment 3•1 year ago
|
||
Hello all, let me know if you need anything for the SUMO article.
| Assignee | ||
Comment 4•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Hi Dayani, this is for AI-powered tab groups, a different feature. Can we reopen this?
| Reporter | ||
Comment 6•1 year ago
|
||
Hi, this article request for AI backed tab organization is distinct from the article for Tab Groups. AI Tab Groups are being released to experiment in 138, restricted to en-US locale because some aspects of the experience are not currently supported in other locales. The AI Tab Groups article is currently blocking release to experiment in 138.
The reason we need this article for an experiment is that both Legal and Trust and Safety teams have said the article is needed before the feature can be defaulted on in Nightly, Beta, and released via experiment in Release channel.
Two points are important:
- "On-device AI" (or in our parlance: machine learning models that run locally) is more private and secure than other implementations we've seen in competitor browsers. For example, some competitor browsers make users sign an agreement that says "Humans may review your tab titles and URLs."
- This is an early stage effort and we have taken steps to ensure that unexpectedly unsafe or objectionable terms are not suggested as group titles, and we intend to gather feedback to improve this and all aspects of the experience during this experimental phase.
Thanks for helping us get this into people's hands so we can figure out what's needed to make if the best it can be.
| Reporter | ||
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Drafted the article, sharing with legal for review now.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 8•1 year ago
|
||
Related SUMO KB article, just approved: https://support.mozilla.org/en-US/kb/how-use-ai-enhanced-tab-groups
Comment 9•1 year ago
|
||
:Stefan is this considered resolved given https://bugzilla.mozilla.org/show_bug.cgi?id=1953899#c8?
| Reporter | ||
Comment 10•1 year ago
|
||
Yes, this is resolved. Thanks for staying flexible as we discovered mid-way through the process that there was a legal need to publish the article sooner than we had originally thought.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Description
•