## 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.** Yes, I have reviewed the FAQ guidelines. ## 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)’.** **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, this content is not under embargo. ## 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/ 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. [REQUIRED] ##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. These finalized changes are available in production. The look and feel of the menus in Desktop Reader View have been updated. New functionality has been added, including the ability to add custom color schemes and additional text formatting options. ## 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, 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 release. ## What is the anticipated release date? [REQUIRED] **Note: Content is typically published at, or within, 48 hours of the release.** Anticipated at release. ## 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.** TBD ## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED] [Bug 1874981 - [Meta] Reader View Comfort Settings](https://bugzilla.mozilla.org/show_bug.cgi?id=1874981) ## 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'** TBD ## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED] The prefs `reader.improved_text_menu.enabled` and `reader.colors_menu.enabled` should both be `true`, which should be the default behavior in 129 ([Bug 1899366 - Flip prefs to enable new text and layout + theme menus by default](https://bugzilla.mozilla.org/show_bug.cgi?id=1899366)). ## 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]** TBD Summary [Product V129]
Bug 1910697 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
## 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.** Yes, I have reviewed the FAQ guidelines. ## 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)’.** **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, this content is not under embargo. ## 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/ 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. [REQUIRED] ##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. These finalized changes are available in production. The look and feel of the menus in Desktop Reader View have been updated. New functionality has been added, including the ability to add custom color schemes and additional text formatting options. ## 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, 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 release. ## What is the anticipated release date? [REQUIRED] **Note: Content is typically published at, or within, 48 hours of the release.** Anticipated at release. ## 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, all languages ## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED] [Bug 1874981 - [Meta] Reader View Comfort Settings](https://bugzilla.mozilla.org/show_bug.cgi?id=1874981) ## 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'** TBD ## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED] The prefs `reader.improved_text_menu.enabled` and `reader.colors_menu.enabled` should both be `true`, which should be the default behavior in 129 ([Bug 1899366 - Flip prefs to enable new text and layout + theme menus by default](https://bugzilla.mozilla.org/show_bug.cgi?id=1899366)). ## 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, Cieara :cmkm can approve Summary [Product V129]
## 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.** Yes, I have reviewed the FAQ guidelines. ## 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)’.** **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, this content is not under embargo. ## 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/ 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. [REQUIRED] ##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. These finalized changes are available in production. The look and feel of the menus in Desktop Reader View have been updated. New functionality has been added, including the ability to add custom color schemes and additional text formatting options. ## 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, 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 release. ## What is the anticipated release date? [REQUIRED] **Note: Content is typically published at, or within, 48 hours of the release.** Anticipated at release. ## 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, all languages ## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED] [Bug 1874981 - [Meta] Reader View Comfort Settings](https://bugzilla.mozilla.org/show_bug.cgi?id=1874981) ## 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 attachments. ## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED] The prefs `reader.improved_text_menu.enabled` and `reader.colors_menu.enabled` should both be `true`, which should be the default behavior in 129 ([Bug 1899366 - Flip prefs to enable new text and layout + theme menus by default](https://bugzilla.mozilla.org/show_bug.cgi?id=1899366)). ## 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, Cieara :cmkm can approve Summary [Product V129]