Private Tab Persistance - Bring back "Close Private tabs" option [iOS V129]
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: nfurlan, Assigned: lsiebert)
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.
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 iOS
Select the type of request.
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]
We need to put back the article that we had before but now the behavior is the other way around. The option is by default ON, meaning that all private tabs will be closed after app closing. If the user wants, they can turn it off and persist their tabs.
##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.
Release FX 129
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].
FX 129
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
August 6
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.
Same languages as before.
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
https://mozilla-hub.atlassian.net/browse/FXIOS-9519
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://mozilla-hub.atlassian.net/browse/FXIOS-9519
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
It is on FX 129 beta.
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]
Andy Furlan
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 3•1 year ago
|
||
Updated article: https://support.mozilla.org/en-US/kb/automatically-close-private-tabs-when-leaving-priv
Comment 4•1 year ago
|
||
(In reply to Lucas Siebert from comment #3)
Updated article: https://support.mozilla.org/en-US/kb/automatically-close-private-tabs-when-leaving-priv
The article title was also updated, from "Automatically close Private Tabs when leaving Private Browsing" to the current title, "Keep Private Browsing tabs open after exiting Firefox". Should we also update the slug, which is still automatically-close-private-tabs-when-leaving-priv ?
Assignee | ||
Comment 5•10 months ago
|
||
(In reply to Alice Wyman from comment #4)
(In reply to Lucas Siebert from comment #3)
Updated article: https://support.mozilla.org/en-US/kb/automatically-close-private-tabs-when-leaving-priv
The article title was also updated, from "Automatically close Private Tabs when leaving Private Browsing" to the current title, "Keep Private Browsing tabs open after exiting Firefox". Should we also update the slug, which is still automatically-close-private-tabs-when-leaving-priv ?
Hey Alice, sorry for the late response—this slipped by me. I usually avoid changing slugs to prevent any issues with SUMO or external links pointing to the content.
Assignee | ||
Comment 6•10 months ago
|
||
(In reply to Lucas Siebert from comment #5)
(In reply to Alice Wyman from comment #4)
(In reply to Lucas Siebert from comment #3)
Updated article: https://support.mozilla.org/en-US/kb/automatically-close-private-tabs-when-leaving-priv
The article title was also updated, from "Automatically close Private Tabs when leaving Private Browsing" to the current title, "Keep Private Browsing tabs open after exiting Firefox". Should we also update the slug, which is still automatically-close-private-tabs-when-leaving-priv ?
Hey Alice, sorry for the late response—this slipped by me. I usually avoid changing slugs to prevent any issues with SUMO or external links pointing to the content.
Thanks for flagging it, Alice! Just post a reply in the discussion.
Description
•