From d1959c0496537dea3608ed72fba351c57bb20c02 Mon Sep 17 00:00:00 2001 From: Simeon Vincent Date: Tue, 22 Jul 2025 16:38:07 -0700 Subject: [PATCH 1/2] Clarify how other browsers handle the BSS key --- .../documentation/develop/extensions-and-the-add-on-id.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/documentation/develop/extensions-and-the-add-on-id.md b/src/content/documentation/develop/extensions-and-the-add-on-id.md index d0ee621bc..9f734c575 100644 --- a/src/content/documentation/develop/extensions-and-the-add-on-id.md +++ b/src/content/documentation/develop/extensions-and-the-add-on-id.md @@ -112,10 +112,10 @@ See [`browser_specific_settings` in manifest.json](https://developer.mozilla.org
- + ## Working without an ID in Manifiest V2 -An add-on ID is optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. One advantage of this is that Google Chrome does not recognize the `browser_specific_settings` key and shows a warning if you include it. +An add-on ID is optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. One advantage of this is that Google Chrome ignores the `browser_specific_settings` manifest key and Apple Safari ignores Firefox's `gecko` and `gecko_android` sub-keys. However, there are some implications of not setting an add-on ID that are described in this section. From f4eb2457016e1fafa01c7784661b625d754c85d0 Mon Sep 17 00:00:00 2001 From: Simeon Vincent Date: Fri, 25 Jul 2025 13:03:33 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: rebloor --- .../documentation/develop/extensions-and-the-add-on-id.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/documentation/develop/extensions-and-the-add-on-id.md b/src/content/documentation/develop/extensions-and-the-add-on-id.md index 9f734c575..3c6634daa 100644 --- a/src/content/documentation/develop/extensions-and-the-add-on-id.md +++ b/src/content/documentation/develop/extensions-and-the-add-on-id.md @@ -115,7 +115,7 @@ See [`browser_specific_settings` in manifest.json](https://developer.mozilla.org ## Working without an ID in Manifiest V2 -An add-on ID is optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. One advantage of this is that Google Chrome ignores the `browser_specific_settings` manifest key and Apple Safari ignores Firefox's `gecko` and `gecko_android` sub-keys. +An add-on ID is optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. However, if you do add the `browser_specific_settings` manifest key (to add an ID), Google Chrome ignores it, and Apple Safari ignores Firefox's `gecko` and `gecko_android` sub-keys. However, there are some implications of not setting an add-on ID that are described in this section.