2042371 - Update https://support.mozilla.org/en-US/kb/permission-request-messages-firefox-extensions (local file access permission) [Firefox for Desktop V153]

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Content, task)

Description

[Rob Wu [:robwu]]

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.

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.

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 / macOS / Linux)

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
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]

Add a heading with "Access local files on your computer" to https://support.mozilla.org/en-US/kb/permission-request-messages-firefox-extensions underneath the existing "Access your data for all websites" section.

This heading matches the in-product string for the permission and localizations of the article should use the same string, identified by webext-perms-host-description-file-urls in extensions.ftl. Once translations catch up following the landing of the feature, strings will be available at https://searchfox.org/l10n/search?q=webext-perms-host-description-file-urls

The extension could read the content of any local file opened in the browser, as well as data you enter into those local web pages.

This access is optional, and is not displayed in the initial install dialog. If requested, file access can be managed as documented at Manage optional permissions for Firefox extensions.

About the last sentence: most other permissions listed there are displayed in install-time permission prompts, runtime permission prompts and about:addons. This new permission is NOT displayed at install time. Instead, users who want to grant extensions access to local files can do so via about:addons, via optional permissions as documented at https://support.mozilla.org/en-US/kb/manage-optional-permissions-extensions (the screenshots there are outdated, but the concepts are still the same)

File access is not a new capability. It was historically part of the "Access your data for all websites" permission, but is being separated from that common permission to allow users to give access to any website without also granting access to local files. Historical context and the motivation for the change is in bug 2034168.

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.

Firefox 153 release (when bug 2034168 lands).

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.

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.

July 21, 2026 (the release date of Firefox 153 - https://whattrainisitnow.com/release/?version=153 ).

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. But if the content is ready sooner, don't wait for the specific date, because the documentation can benefit pre-release users.

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.

This new section should (eventually) be added to all localized versions of the article.

According to https://support.mozilla.org/en-US/kb/permission-request-messages-firefox-extensions/show_translations
the article is localized in 32 other languages:

ar, bg, cs, da, de, el, es, fi, fr, hi-IN, hr, hu, id, it, ja, ka, ko, lt, nl, no, pl, pt-BR, pt-PT, ru, sr, th, tr, uk, ur, vi, zh-CN, zh-TW

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

• bug 2034168

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'

No separate design assets, this is a new string in existing UI.

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

1. Install an extension requesting <all_urls> or file:///* permissions, such as https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/
2. Visit about:addons, go to "Permissions and data"
3. There should be an "Optional:" section listing a toggle with the "Access local files on your computer" label (or the localized variants of these strings).

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.

Comment 1

[mcalidonio]

Asana: https://app.asana.com/1/90589597529/project/1203460865189761/task/1215204137585217?focus=true

Comment 2

[Flavius Floare]

Rob, I tagged you, so you can take a look at the update: https://docs.google.com/document/d/1Np3WkTQZqqml11Os1fB4_Ut5sE1tyQhPWNsqHusjNP4/edit?tab=t.0

Comment 3

[Rob Wu [:robwu]]

Thanks for the quick action! I posted feedback in the doc. It looks like the best course of action to avoid duplicating information may be to simply update the screenshots in the other existing article I already mentioned in my initial comment:

optional permissions as documented at https://support.mozilla.org/en-US/kb/manage-optional-permissions-extensions (the screenshots there are outdated, but the concepts are still the same)

Comment 4

[Flavius Floare]

Updated here: https://support.mozilla.org/en-US/kb/permission-request-messages-firefox-extensions
Also updated this one, as part of this bug: https://support.mozilla.org/en-US/kb/manage-optional-permissions-extensions