Bug 2012297 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]

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]

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)

Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)


## 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]

On desktop Firefox, we are combining the functionality of the address bar's Lock icon (for providing the current tab's site information) and Shield icon (for protections specific to both the current tab's protection applied and general protection settings) into a single Shield icon that displays both types of information into a Unified Trust Panel.

Articles such as https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop make reference to the lock and shield with corresponding screenshots, and will need to account for the single icon and new Unified Trust Panel.

##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production

## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

They will neither be region specific nor release via gradual rollout.

## Please indicate if this is an on- or off-train release [REQUIRED] 

On-train in Fx 149 Release

## What is the anticipated release date? [REQUIRED]

March 24, 2026

## 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]

all supported

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://bugzilla.mozilla.org/show_bug.cgi?id=1964725

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://www.figma.com/file/fYqZbJCyoO4IO0LxgSRWW8?node-id=7800%3A46149&mode=dev

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

- set `browser.urlbar.trustPanel.featureGate` if it isn't already

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes, Gayatri Pendse
## Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

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]

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)

Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)


## 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]

On desktop Firefox, we are combining the functionality of the address bar's Lock icon (for providing the current tab's site information) and Shield icon (for protections specific to both the current tab's protection applied and general protection settings) into a single Shield icon that displays both types of information into a Unified Trust Panel.

Articles such as https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop make reference to the lock and shield with corresponding screenshots, and will need to account for the single icon and new Unified Trust Panel.

## Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production

## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

They will neither be region specific nor release via gradual rollout.

## Please indicate if this is an on- or off-train release [REQUIRED] 

On-train in Fx 149 Release

## What is the anticipated release date? [REQUIRED]

March 24, 2026

## 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]

all supported

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://bugzilla.mozilla.org/show_bug.cgi?id=1964725

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://www.figma.com/file/fYqZbJCyoO4IO0LxgSRWW8?node-id=7800%3A46149&mode=dev

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

- set `browser.urlbar.trustPanel.featureGate` if it isn't already

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes, Gayatri Pendse
## Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

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]

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)

Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)


## 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]

On desktop Firefox, we are combining the functionality of the address bar's Lock icon (for providing the current tab's site information) and Shield icon (for protections specific to both the current tab's protection applied and general protection settings) into a single Shield icon that displays both types of information into a Unified Trust Panel.

Articles such as https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop make reference to the lock and shield with corresponding screenshots, and will need to account for the single icon and new Unified Trust Panel.

## Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production (Release), but also applicable to Fx 149+ Beta and Nightly.

## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

They will neither be region specific nor release via gradual rollout.

## Please indicate if this is an on- or off-train release [REQUIRED] 

On-train in Fx 149 Release

## What is the anticipated release date? [REQUIRED]

March 24, 2026

## 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]

all supported

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://bugzilla.mozilla.org/show_bug.cgi?id=1964725

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://www.figma.com/file/fYqZbJCyoO4IO0LxgSRWW8?node-id=7800%3A46149&mode=dev

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

- set `browser.urlbar.trustPanel.featureGate` if it isn't already

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes, Gayatri Pendse
## Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

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]

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)

Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)


## 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]

On desktop Firefox, we are combining the functionality of the address bar's Lock icon (for providing the current tab's site information) and Shield icon (for protections specific to both the current tab's protection applied and general protection settings) into a single Shield icon that displays both types of information into a Unified Trust Panel.

Articles such as https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop make reference to the lock and shield with corresponding screenshots, and will need to account for the single icon and new Unified Trust Panel.

## Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production (Release), but also applicable to Fx 149+ Beta and Nightly.

## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

They will neither be region specific nor release via gradual rollout.

## Please indicate if this is an on- or off-train release [REQUIRED] 

On-train in Fx 149 Release

## What is the anticipated release date? [REQUIRED]

March 24, 2026

## 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]

all supported languages

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://bugzilla.mozilla.org/show_bug.cgi?id=1964725

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://www.figma.com/file/fYqZbJCyoO4IO0LxgSRWW8?node-id=7800%3A46149&mode=dev

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

- set `browser.urlbar.trustPanel.featureGate` if it isn't already

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes, Gayatri Pendse
## Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

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]

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)

Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)


## 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]

On desktop Firefox, we are combining the functionality of the address bar's Lock icon (for providing the current tab's site information) and Shield icon (for protections specific to both the current tab's protection applied and general protection settings) into a single Shield icon that displays both types of information into a Unified Trust Panel.

Articles such as https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop make reference to the lock and shield with corresponding screenshots, and will need to account for the single icon and new Unified Trust Panel.

## Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]

Production (Release), but also applicable to Fx 149+ Beta and Nightly.

## Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

They will neither be region specific nor release via gradual rollout.

## Please indicate if this is an on- or off-train release [REQUIRED] 

On-train in Fx 149 Release

## What is the anticipated release date? [REQUIRED]

March 24, 2026

## 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]

all supported languages

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://bugzilla.mozilla.org/show_bug.cgi?id=1964725

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://www.figma.com/file/fYqZbJCyoO4IO0LxgSRWW8?node-id=7800%3A46149&mode=dev

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

- set `browser.urlbar.trustPanel.featureGate` to `true` if it isn't already

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes, Gayatri Pendse

Back to Bug 2012297 Comment 0