diff --git a/files/en-us/glossary/cacheable/index.md b/files/en-us/glossary/cacheable/index.md index 671c61b708b6863..e596168ed1d9025 100644 --- a/files/en-us/glossary/cacheable/index.md +++ b/files/en-us/glossary/cacheable/index.md @@ -6,7 +6,7 @@ page-type: glossary-definition A **cacheable** response is an HTTP response that can be cached, that is stored to be retrieved and used later, saving a new request to the server. Not all HTTP responses can be cached, these are the following constraints for an HTTP response to be cached: -- The method used in the request is itself _cacheable_, that is either a {{HTTPMethod("GET")}} or a {{HTTPMethod("HEAD")}} method. A response to a {{HTTPMethod("POST")}} or {{HTTPMethod("PATCH")}} request can also be cached if freshness is indicated and the {{HTTPHeader("Content-Location")}} header is set, but this is rarely implemented. (For example, Firefox does not support it per .) Other methods, like {{HTTPMethod("PUT")}} or {{HTTPMethod("DELETE")}} are not cacheable and their result cannot be cached. +- The method used in the request is itself _cacheable_, that is either a {{HTTPMethod("GET")}} or a {{HTTPMethod("HEAD")}} method. A response to a {{HTTPMethod("POST")}} or {{HTTPMethod("PATCH")}} request can also be cached if freshness is indicated and the {{HTTPHeader("Content-Location")}} header is set, but this is rarely implemented. For example, Firefox does not support it ([Firefox bug 109553](https://bugzil.la/109553)). Other methods, like {{HTTPMethod("PUT")}} or {{HTTPMethod("DELETE")}} are not cacheable and their result cannot be cached. - The status code of the response is _known_ by the application caching, and it is considered _cacheable_. The following status code are cacheable: {{HTTPStatus("200")}}, {{HTTPStatus("203")}}, {{HTTPStatus("204")}}, {{HTTPStatus("206")}}, {{HTTPStatus("300")}}, {{HTTPStatus("301")}}, {{HTTPStatus("404")}}, {{HTTPStatus("405")}}, {{HTTPStatus("410")}}, {{HTTPStatus("414")}}, and {{HTTPStatus("501")}}. - There are _specific headers_ in the response, like {{HTTPHeader("Cache-Control")}}, that prevents caching. diff --git a/files/en-us/glossary/forbidden_header_name/index.md b/files/en-us/glossary/forbidden_header_name/index.md index 53bc3ed9ea19150..20c14a584a14557 100644 --- a/files/en-us/glossary/forbidden_header_name/index.md +++ b/files/en-us/glossary/forbidden_header_name/index.md @@ -33,7 +33,7 @@ Forbidden header names start with `Proxy-` or `Sec-`, or are one of the followin - {{HTTPHeader("Upgrade")}} - {{HTTPHeader("Via")}} -> **Note:** The {{HTTPHeader("User-Agent")}} header is no longer forbidden, [as per spec](https://fetch.spec.whatwg.org/#terminology-headers) — see forbidden header name list (this was implemented in Firefox 43) — it can now be set in a Fetch [Headers](/en-US/docs/Web/API/Headers) object, or with the [setRequestHeader()](/en-US/docs/Web/API/XMLHttpRequest/setRequestHeader) method of `XMLHttpRequest`. However, Chrome will silently drop the header from Fetch requests (see [Chromium bug 571722](https://bugs.chromium.org/p/chromium/issues/detail?id=571722)). +> **Note:** The {{HTTPHeader("User-Agent")}} header is no longer forbidden, [as per spec](https://fetch.spec.whatwg.org/#terminology-headers) — see forbidden header name list (this was implemented in Firefox 43) — it can now be set in a Fetch [Headers](/en-US/docs/Web/API/Headers) object, or with the [setRequestHeader()](/en-US/docs/Web/API/XMLHttpRequest/setRequestHeader) method of `XMLHttpRequest`. However, Chrome will silently drop the header from Fetch requests (see [Chromium bug 571722](https://crbug.com/571722)). ## See also diff --git a/files/en-us/glossary/quality_values/index.md b/files/en-us/glossary/quality_values/index.md index 34e2c639c6a4893..4e476e28ec77528 100644 --- a/files/en-us/glossary/quality_values/index.md +++ b/files/en-us/glossary/quality_values/index.md @@ -42,7 +42,7 @@ Some syntax, like the one of {{HTTPHeader("Accept")}}, allow additional specifie ### Firefox -Starting with Firefox 18, the quality factor values are clamped to 2 decimal places. They used to be clamped to only 1 decimal place in earlier versions ({{bug(672448)}}). +Starting with Firefox 18, the quality factor values are clamped to 2 decimal places. They used to be clamped to only 1 decimal place in earlier versions ([Firefox bug 672448](https://bugzil.la/672448)). ## More information diff --git a/files/en-us/glossary/tls/index.md b/files/en-us/glossary/tls/index.md index d04006259173c15..36bd2dd97cb98d1 100644 --- a/files/en-us/glossary/tls/index.md +++ b/files/en-us/glossary/tls/index.md @@ -8,7 +8,7 @@ page-type: glossary-definition All modern browsers support the TLS protocol, requiring the server to provide a valid {{Glossary("Digital certificate", "digital certificate")}} confirming its identity in order to establish a secure connection. It is possible for both the client and server to mutually authenticate each other, if both parties provide their own individual digital certificates. -> **Note:** All major browsers began removing support for TLS 1.0 and 1.1 in early 2020; you'll need to make sure your web server supports TLS 1.2 or 1.3 going forward. From version 74 onwards, Firefox will return a [Secure Connection Failed](https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect) error when connecting to servers using the older TLS versions ({{bug(1606734)}}). +> **Note:** All major browsers began removing support for TLS 1.0 and 1.1 in early 2020; you'll need to make sure your web server supports TLS 1.2 or 1.3 going forward. From version 74 onwards, Firefox will return a [Secure Connection Failed](https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect) error when connecting to servers using the older TLS versions ([Firefox bug 1606734](https://bugzil.la/1606734)). ## See also diff --git a/files/en-us/learn/accessibility/css_and_javascript/index.md b/files/en-us/learn/accessibility/css_and_javascript/index.md index f359c1c5de88970..f56864fb3b04009 100644 --- a/files/en-us/learn/accessibility/css_and_javascript/index.md +++ b/files/en-us/learn/accessibility/css_and_javascript/index.md @@ -308,7 +308,7 @@ function createLink(testItem) { Each link serves a dual purpose — it tells you what the error is, plus you can click on it/activate it to jump straight to the input element in question and correct your entry. -> **Note:** The `focus()` part of this example is a bit tricky. Chrome and Edge (and newer versions of IE) will focus the element when the link is clicked, without needing the `onclick`/`focus()` block. Safari will only highlight the form element with the link on its own, so needs the `onclick`/`focus()` block to actually focus it. Firefox doesn't focus the inputs properly at all in this context, so Firefox users can't take advantage of this at present (although everything else works fine). The Firefox issue should be fixed soon — work is being done to give Firefox behavior parity with other browsers (see {{bug(277178)}}). +> **Note:** The `focus()` part of this example is a bit tricky. Chrome and Edge (and newer versions of IE) will focus the element when the link is clicked, without needing the `onclick`/`focus()` block. Safari will only highlight the form element with the link on its own, so needs the `onclick`/`focus()` block to actually focus it. Firefox doesn't focus the inputs properly at all in this context, so Firefox users can't take advantage of this at present (although everything else works fine). The Firefox issue should be fixed soon — work is being done to give Firefox behavior parity with other browsers (see [Firefox bug 277178](https://bugzil.la/277178)). In addition, the `errorField` is placed at the top of the source order (although it is positioned differently in the UI using CSS), meaning that users can find out exactly what's wrong with their form submissions and get to the input elements in question by going back up to the start of the page. diff --git a/files/en-us/learn/common_questions/design_and_accessibility/html_features_for_accessibility/index.md b/files/en-us/learn/common_questions/design_and_accessibility/html_features_for_accessibility/index.md index 9e2442b47937dd6..548a54a3f38dffb 100644 --- a/files/en-us/learn/common_questions/design_and_accessibility/html_features_for_accessibility/index.md +++ b/files/en-us/learn/common_questions/design_and_accessibility/html_features_for_accessibility/index.md @@ -81,7 +81,7 @@ The `alt` attribute for the same content may vary depending on the context. In t ## ARIA role attribute -By default, all semantic elements in HTML have a [`role`](/en-US/docs/Web/Accessibility/ARIA/Roles); for example, `` has the `radio` role. Non-semantic elements in HTML do not have a role. ARIA roles can be used to describe elements that don't natively exist in HTML, such as a [`tablist`](/en-US/docs/Web/Accessibility/ARIA/Roles/tablist_role) widget. Roles are also helpful for newer elements that exist but don't yet have full browser support. For example, when using SVG images, add `role="img"` to the opening tag, as there is an [SVG VoiceOver bug](https://bugs.webkit.org/show_bug.cgi?id=216364) whereby VoiceOver does not correctly announce SVG images. +By default, all semantic elements in HTML have a [`role`](/en-US/docs/Web/Accessibility/ARIA/Roles); for example, `` has the `radio` role. Non-semantic elements in HTML do not have a role. ARIA roles can be used to describe elements that don't natively exist in HTML, such as a [`tablist`](/en-US/docs/Web/Accessibility/ARIA/Roles/tablist_role) widget. Roles are also helpful for newer elements that exist but don't yet have full browser support. For example, when using SVG images, add `role="img"` to the opening tag, as there is an [SVG VoiceOver bug](https://webkit.org/b/216364) whereby VoiceOver does not correctly announce SVG images. ```html MDN logo diff --git a/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.md b/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.md index f1232a87645e1f7..5558fdb01dbe2f0 100644 --- a/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.md +++ b/files/en-us/learn/tools_and_testing/cross_browser_testing/javascript/index.md @@ -436,7 +436,7 @@ Many developers implemented bad browser sniffing code and didn't maintain it, an The lesson to be learned here is to never use browser sniffing. The only real use case for browser sniffing code in the modern day is if you are implementing a fix for a bug in a very specific version of a particular browser. But even then, most bugs get fixed pretty quickly in browser vendor rapid release cycles. It won't come up very often. [Feature detection](#feature_detection) is almost always a better option — if you detect whether a feature is supported, you won't need to change your code when new browser versions come out, and the tests are much more reliable. -If you come across browser sniffing when joining an existing project, look at whether it can be replaced with something more sensible. Browser sniffing causes all kind of interesting bugs, like {{bug(1308462)}}. +If you come across browser sniffing when joining an existing project, look at whether it can be replaced with something more sensible. Browser sniffing causes all kind of interesting bugs, like [Firefox bug 1308462](https://bugzil.la/1308462). ### Handling JavaScript prefixes diff --git a/files/en-us/mdn/writing_guidelines/howto/tag/index.md b/files/en-us/mdn/writing_guidelines/howto/tag/index.md index 7fb767d713a2efc..74f42991c212de7 100644 --- a/files/en-us/mdn/writing_guidelines/howto/tag/index.md +++ b/files/en-us/mdn/writing_guidelines/howto/tag/index.md @@ -178,7 +178,7 @@ Generally, all articles should have at _least_ a "[document type](#document_type ### Tags that don't follow our tagging standards Please fix any documents that have tags that don't follow the standards described on this page. -Note that you may occasionally see some localized tags (such as `Référence`) showing up on some English pages. This was due to a [bug in Kuma](https://bugzilla.mozilla.org/show_bug.cgi?id=776048), which caused the tags to reappear even if they were deleted. That bug has [since been fixed](https://bugzilla.mozilla.org/show_bug.cgi?id=776048#c37), so any remaining localized tags can be cleaned up if they're spotted. +Note that you may occasionally see some localized tags (such as `Référence`) showing up on some English pages. This was due to a [bug in Kuma](https://bugzil.la/776048), which caused the tags to reappear even if they were deleted. That bug has [since been fixed](https://bugzil.la/776048#c37), so any remaining localized tags can be cleaned up if they're spotted. ### Incorrect tags diff --git a/files/en-us/mdn/writing_guidelines/howto/write_an_api_reference/information_contained_in_a_webidl_file/index.md b/files/en-us/mdn/writing_guidelines/howto/write_an_api_reference/information_contained_in_a_webidl_file/index.md index 3792fc0a19bc85a..f100dd7eb8bd0b0 100644 --- a/files/en-us/mdn/writing_guidelines/howto/write_an_api_reference/information_contained_in_a_webidl_file/index.md +++ b/files/en-us/mdn/writing_guidelines/howto/write_an_api_reference/information_contained_in_a_webidl_file/index.md @@ -457,7 +457,7 @@ The iterator will iterate over values of type _valueType_, with keys of type _ke - `entries()` that returns an [`iterator`](/en-US/docs/Web/JavaScript/Reference/Iteration_protocols) on the indexes (of type _keyType_). E.g. {{domxref('FormData.entries()')}} - `values()` that returns an [`iterator`](/en-US/docs/Web/JavaScript/Reference/Iteration_protocols) on the values. E.g. {{domxref('FormData.values()')}} - `keys()` that returns an [`iterator`](/en-US/docs/Web/JavaScript/Reference/Iteration_protocols) on the keys. E.g. {{domxref('FormData.keys()')}} -- Once {{bug(1216751)}} lands, `forEach()`. +- Once [Firefox bug 1216751](https://bugzil.la/1216751) lands, `forEach()`. Such an iterator allows to use the syntax `for (const p in object)` as a shorthand of `for (const p in object.entries())`. We add a sentence about it in the interface description. E.g. {{domxref('FormData')}}. diff --git a/files/en-us/mdn/writing_guidelines/page_structures/macros/commonly_used_macros/index.md b/files/en-us/mdn/writing_guidelines/page_structures/macros/commonly_used_macros/index.md index f2d2c85c1071944..8c86e8226416113 100644 --- a/files/en-us/mdn/writing_guidelines/page_structures/macros/commonly_used_macros/index.md +++ b/files/en-us/mdn/writing_guidelines/page_structures/macros/commonly_used_macros/index.md @@ -165,10 +165,10 @@ Most macros will also take a second argument allowing you to change the display - Bugs - - [`bug`](https://github.com/mdn/yari/blob/main/kumascript/macros/bug.ejs) allows you to link to a bug on bugzilla.mozilla.org easily using this syntax: `\{{Bug(123456)}}`. - This gives you: {{Bug(123456)}}. + - [`bug`](https://github.com/mdn/yari/blob/main/kumascript/macros/bug.ejs) allows you to link to a bug on bugzilla.mozilla.org easily using this syntax: `\[Webkit bug 123456](https://bugzil.la/123456)`. + This gives you: [Webkit bug 123456](https://bugzil.la/123456). - [`WebkitBug`](https://github.com/mdn/yari/blob/main/kumascript/macros/WebkitBug.ejs) inserts a link to a bug in the WebKit bug database. - For example, `\{{WebkitBug(31277)}}` inserts {{WebkitBug(31277)}}. + For example, `\[Webkit bug 31277](https://webkit.org/b/31277)` inserts [Webkit bug 31277](https://webkit.org/b/31277). ### Navigation aids for multi-page guides diff --git a/files/en-us/mozilla/add-ons/webextensions/api/extension/getbackgroundpage/index.md b/files/en-us/mozilla/add-ons/webextensions/api/extension/getbackgroundpage/index.md index 6b4ee5a8a7340c4..8ae3544d57d91b0 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/extension/getbackgroundpage/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/extension/getbackgroundpage/index.md @@ -21,7 +21,7 @@ Returns the [Window](/en-US/docs/Web/API/Window) of the background page if the b This a synchronous function. -> **Note:** This method cannot be used in Private Browsing mode — it always returns null. Consider using {{WebExtAPIRef("runtime.sendMessage","runtime.sendMessage()")}} or {{WebExtAPIRef("runtime.connect","runtime.connect()")}}. See {{bug(1329304)}} for more information. +> **Note:** This method cannot be used in Private Browsing mode — it always returns null. Consider using {{WebExtAPIRef("runtime.sendMessage","runtime.sendMessage()")}} or {{WebExtAPIRef("runtime.connect","runtime.connect()")}}. See [Firefox bug 1329304](https://bugzil.la/1329304) for more information. ## Syntax diff --git a/files/en-us/mozilla/add-ons/webextensions/api/menus/create/index.md b/files/en-us/mozilla/add-ons/webextensions/api/menus/create/index.md index 89e12d68aeb10d3..8048bf0297559cf 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/menus/create/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/menus/create/index.md @@ -107,7 +107,7 @@ browser.menus.create( Only the first ampersand will be used to set an access key: subsequent ampersands will not be displayed but will not set keys. So "\&A and \&B" will be shown as "A and B" and set "A" as the access key. - In some localized versions of Firefox (Japanese and Chinese), the access key is surrounded by parentheses and appended to the menu label, _unless_ the menu title itself already ends with the access key (`"toolkit(&K)"` for example). For more details, see {{bug(1647373)}}. + In some localized versions of Firefox (Japanese and Chinese), the access key is surrounded by parentheses and appended to the menu label, _unless_ the menu title itself already ends with the access key (`"toolkit(&K)"` for example). For more details, see [Firefox bug 1647373](https://bugzil.la/1647373). - `type` {{optional_inline}} - : `{{WebExtAPIRef('menus.ItemType')}}`. The type of menu item: "normal", "checkbox", "radio", "separator". Defaults to "normal". diff --git a/files/en-us/mozilla/add-ons/webextensions/api/permissions/request/index.md b/files/en-us/mozilla/add-ons/webextensions/api/permissions/request/index.md index dfc5f1b29bb3f09..286e4762276ebe5 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/permissions/request/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/permissions/request/index.md @@ -80,6 +80,6 @@ document.querySelector("#request").addEventListener("click", requestPermissions) {{WebExtExamples}} -> **Note:** Currently has a [bug with requesting origins](https://bugzilla.mozilla.org/show_bug.cgi?id=1411873) and [requesting permissions on the about:addons page](https://bugzilla.mozilla.org/show_bug.cgi?id=1382953). +> **Note:** Currently has a [bug with requesting origins](https://bugzil.la/1411873) and [requesting permissions on the about:addons page](https://bugzil.la/1382953). > **Note:** This API is based on Chromium's [`chrome.permissions`](https://developer.chrome.com/docs/extensions/reference/permissions/) API. diff --git a/files/en-us/mozilla/add-ons/webextensions/api/runtime/getbackgroundpage/index.md b/files/en-us/mozilla/add-ons/webextensions/api/runtime/getbackgroundpage/index.md index a412334b8e1e1ef..cdb7c026c486175 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/runtime/getbackgroundpage/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/runtime/getbackgroundpage/index.md @@ -23,13 +23,13 @@ This provides a convenient way for other privileged extension scripts to get dir Note that variables that were declared using [`const`](/en-US/docs/Web/JavaScript/Reference/Statements/const) or [`let`](/en-US/docs/Web/JavaScript/Reference/Statements/let) do not appear in the `Window` object returned by this function. -**Also note that this method cannot be used in a private window in Firefox**—it always returns `null`. For more info see [related bug at bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1329304). +**Also note that this method cannot be used in a private window in Firefox**—it always returns `null`. For more info see [related bug at bugzilla](https://bugzil.la/1329304). If the background page is an event page, the system will ensure it is loaded before resolving the promise. This is an asynchronous function that returns a {{JSxRef("Promise")}}. -> **Note:** In Firefox, this method cannot be used in Private Browsing mode — it always returns `null`. For more info see {{bug(1329304)}}. +> **Note:** In Firefox, this method cannot be used in Private Browsing mode — it always returns `null`. For more info see [Firefox bug 1329304](https://bugzil.la/1329304). > > In Chrome, this method is available only with persistent background pages, which are not available in Manifest V3, so consider using Manifest V2. See the [this](https://developer.chrome.com/docs/extensions/mv3/migrating_to_service_workers/) for details. > diff --git a/files/en-us/mozilla/add-ons/webextensions/api/scripting/executescript/index.md b/files/en-us/mozilla/add-ons/webextensions/api/scripting/executescript/index.md index 319b95ffabb112c..9df6335440c7f97 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/scripting/executescript/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/scripting/executescript/index.md @@ -22,7 +22,7 @@ Injects a script into a target context. The script is run at `document_idle` by To use this API you must have the `"scripting"` [permission](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions) and permission for the target's URL, either explicitly as a [host permission](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions#host_permissions) or using the [activeTab permission](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions#activetab_permission). -In Firefox and Safari, partial lack of host permissions can result in a successful execution (with the partial results in the resolved promise). In Chrome, any missing permission prevents any execution from happening, see ([Issue 1325114](https://bugs.chromium.org/p/chromium/issues/detail?id=1325114))). +In Firefox and Safari, partial lack of host permissions can result in a successful execution (with the partial results in the resolved promise). In Chrome, any missing permission prevents any execution from happening, see ([Issue 1325114](https://crbug.com/1325114))). The scripts you inject are called [content scripts](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts). diff --git a/files/en-us/mozilla/add-ons/webextensions/api/sessions/restore/index.md b/files/en-us/mozilla/add-ons/webextensions/api/sessions/restore/index.md index 7f78506f5901a64..27a5a06e57d241a 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/sessions/restore/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/sessions/restore/index.md @@ -107,4 +107,4 @@ browser.browserAction.onClicked.addListener(() => { ## Known issues -[Bug 1538119](https://bugzilla.mozilla.org/show_bug.cgi?id=1538119) - Duplicate sessionId in browser.sessions.getRecentlyClosed() after "Restore previous session" +[Bug 1538119](https://bugzil.la/1538119) - Duplicate sessionId in browser.sessions.getRecentlyClosed() after "Restore previous session" diff --git a/files/en-us/mozilla/add-ons/webextensions/api/storage/storagearea/getbytesinuse/index.md b/files/en-us/mozilla/add-ons/webextensions/api/storage/storagearea/getbytesinuse/index.md index 15fc47492f5b63d..4544e9a23c8a830 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/storage/storagearea/getbytesinuse/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/storage/storagearea/getbytesinuse/index.md @@ -22,7 +22,7 @@ Gets the amount of storage space, in bytes, used one or more items being stored This function only exists in browser.storage.sync It does not exist in browser.storage.local -See +See This is an asynchronous function that returns a [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise). @@ -34,7 +34,7 @@ let gettingSpace = browser.storage..getBytesInUse( ) ``` -`` can only be {{WebExtAPIRef("storage.sync")}}, not {{WebExtAPIRef("storage.local")}} because of [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1385832). +`` can only be {{WebExtAPIRef("storage.sync")}}, not {{WebExtAPIRef("storage.local")}} because of [this bug](https://bugzil.la/1385832). ### Parameters diff --git a/files/en-us/mozilla/add-ons/webextensions/api/tabs/detectlanguage/index.md b/files/en-us/mozilla/add-ons/webextensions/api/tabs/detectlanguage/index.md index b48f67c314ed45b..0251d71f15a1528 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/tabs/detectlanguage/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/tabs/detectlanguage/index.md @@ -39,7 +39,7 @@ let detecting = browser.tabs.detectLanguage( ### Return value -A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that will be fulfilled with a string representing an ISO language code such as `en` or `fr`. For a complete list of languages supported by this method, see [kLanguageInfoTable](https://src.chromium.org/viewvc/chrome/trunk/src/third_party/cld/languages/internal/languages.cc#l23). For an unknown language, `"und"` will be returned (but see [bug 1288263](https://bugzilla.mozilla.org/show_bug.cgi?id=1288263)). If any error occurs the promise will be rejected with an error message. +A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that will be fulfilled with a string representing an ISO language code such as `en` or `fr`. For a complete list of languages supported by this method, see [kLanguageInfoTable](https://src.chromium.org/viewvc/chrome/trunk/src/third_party/cld/languages/internal/languages.cc#l23). For an unknown language, `"und"` will be returned (but see [bug 1288263](https://bugzil.la/1288263)). If any error occurs the promise will be rejected with an error message. ## Examples diff --git a/files/en-us/mozilla/add-ons/webextensions/api/theme/reset/index.md b/files/en-us/mozilla/add-ons/webextensions/api/theme/reset/index.md index 4805d6ef3c974bd..cb74be571410d7f 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/theme/reset/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/theme/reset/index.md @@ -18,7 +18,7 @@ browser-compat: webextensions.api.theme.reset Resets any theme that was applied using the {{WebExtAPIRef("theme.update()")}} method. -Note that this will always reset the theme back to the original default theme, even if the user had selected a different theme before this extension's theme was applied (see [bug 1415267](https://bugzilla.mozilla.org/show_bug.cgi?id=1415267)). +Note that this will always reset the theme back to the original default theme, even if the user had selected a different theme before this extension's theme was applied (see [bug 1415267](https://bugzil.la/1415267)). ## Syntax diff --git a/files/en-us/mozilla/add-ons/webextensions/api/webrequest/blockingresponse/index.md b/files/en-us/mozilla/add-ons/webextensions/api/webrequest/blockingresponse/index.md index cb4be3211fa182f..69b1d0082ec870a 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/webrequest/blockingresponse/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/webrequest/blockingresponse/index.md @@ -42,7 +42,7 @@ Values of this type are objects. They contain the following properties: - : `string`. This is a URL, and if set, the original request is redirected to that URL. You can only set this property in {{WebExtAPIRef("webRequest.onBeforeRequest", "onBeforeRequest")}} or {{WebExtAPIRef("webRequest.onHeadersReceived", "onHeadersReceived")}}. - Redirections to non-HTTP schemes such as data: are allowed, but they are not currently supported ({{bug("707624")}}). Redirects use the same request method as the original request unless initiated from `onHeadersReceived` stage, in which case the redirect uses the GET method. + Redirections to non-HTTP schemes such as data: are allowed, but they are not currently supported ([Firefox bug 707624](https://bugzil.la/707624)). Redirects use the same request method as the original request unless initiated from `onHeadersReceived` stage, in which case the redirect uses the GET method. If an extension wants to redirect a public (e.g. HTTPS) URL to an [extension page](/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Extension_pages), the extension's manifest.json file must contain a [web_accessible_resources](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/web_accessible_resources) key that lists the URL for the extension page. diff --git a/files/en-us/mozilla/add-ons/webextensions/api/webrequest/onbeforerequest/index.md b/files/en-us/mozilla/add-ons/webextensions/api/webrequest/onbeforerequest/index.md index f8b0d7f1cea9c1b..d4b8d4b24c00784 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/webrequest/onbeforerequest/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/webrequest/onbeforerequest/index.md @@ -183,7 +183,7 @@ Events have three functions: ### DNS resolution ordering when BlockingResponse is used -Regarding DNS resolution when BlockingResponse is used with OnBeforeRequest: In HTTP Channel, onBeforeRequest with blocking response does happen prior to DNS resolution and also prior to speculative connect. For other channels, speculative connect may cause DNS requests to happen before onBeforeRequest. This ordering is not something an extension developer ought to rely on as it may vary across browsers, and from one browser version to another, let alone one request channel to another. Refer [BugZilla issue clarification provided by Mozilla developers on DNS resolution ordering](https://bugzilla.mozilla.org/show_bug.cgi?id=1466099) +Regarding DNS resolution when BlockingResponse is used with OnBeforeRequest: In HTTP Channel, onBeforeRequest with blocking response does happen prior to DNS resolution and also prior to speculative connect. For other channels, speculative connect may cause DNS requests to happen before onBeforeRequest. This ordering is not something an extension developer ought to rely on as it may vary across browsers, and from one browser version to another, let alone one request channel to another. Refer [BugZilla issue clarification provided by Mozilla developers on DNS resolution ordering](https://bugzil.la/1466099) ## Examples diff --git a/files/en-us/mozilla/add-ons/webextensions/chrome_incompatibilities/index.md b/files/en-us/mozilla/add-ons/webextensions/chrome_incompatibilities/index.md index 65b522b98ca8077..b9a74691c2e461c 100644 --- a/files/en-us/mozilla/add-ons/webextensions/chrome_incompatibilities/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/chrome_incompatibilities/index.md @@ -19,12 +19,12 @@ However, there are significant differences between Chrome, Firefox, and Edge. In - JavaScript APIs: - **In Firefox:** JavaScript APIs are accessed under the `browser` namespace. - - **In Chrome and Edge:** JavaScript APIs are accessed under the `chrome` namespace. (cf. [Chrome bug 798169](https://bugs.chromium.org/p/chromium/issues/detail?id=798169)) + - **In Chrome and Edge:** JavaScript APIs are accessed under the `chrome` namespace. (cf. [Chrome bug 798169](https://crbug.com/798169)) - Asynchronous APIs: - **In Firefox:** Asynchronous APIs are implemented using promises. - - **In Chrome and Edge:** Asynchronous APIs are implemented using callbacks. (cf. [Chrome bug 328932](https://bugs.chromium.org/p/chromium/issues/detail?id=328932)) + - **In Chrome and Edge:** Asynchronous APIs are implemented using callbacks. (cf. [Chrome bug 328932](https://crbug.com/328932)) The rest of this page summarizes these and other incompatibilities. @@ -149,7 +149,7 @@ When calling `tabs.remove()`: - **In Firefox:** - Requests can be redirected only if their original URL uses the `http:` or `https:` scheme. - - The `activeTab` permission does not allow intercepting network requests in the current tab. (See [bug 1617479](https://bugzilla.mozilla.org/show_bug.cgi?id=1617479)) + - The `activeTab` permission does not allow intercepting network requests in the current tab. (See [bug 1617479](https://bugzil.la/1617479)) - Events are not fired for system requests (for example, extension upgrades or search bar suggestions). - **From Firefox 57 onwards:** Firefox makes an exception for extensions that need to intercept {{WebExtAPIRef("webRequest.onAuthRequired")}} for proxy authorization. See the documentation for {{WebExtAPIRef("webRequest.onAuthRequired")}}. @@ -170,7 +170,7 @@ When calling `tabs.remove()`: #### DeclarativeContent API -- **In Firefox:** Chrome's [declarativeContent](https://developer.chrome.com/docs/extensions/reference/declarativeContent/) API [has not yet been implemented](https://bugzilla.mozilla.org/show_bug.cgi?id=1435864). In addition, Firefox [will not be supporting](https://bugzilla.mozilla.org/show_bug.cgi?id=1323433#c16) the `declarativeContent.RequestContentScript` API (which is rarely used, and is unavailable in stable releases of Chrome). +- **In Firefox:** Chrome's [declarativeContent](https://developer.chrome.com/docs/extensions/reference/declarativeContent/) API [has not yet been implemented](https://bugzil.la/1435864). In addition, Firefox [will not be supporting](https://bugzil.la/1323433#c16) the `declarativeContent.RequestContentScript` API (which is rarely used, and is unavailable in stable releases of Chrome). ### Miscellaneous incompatibilities @@ -200,7 +200,7 @@ When calling `tabs.remove()`: #### Content script environment -- **In Firefox:** The global scope of the [content script environment](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts#content_script_environment) is not strictly equal to `window` ({{bug(1208775)}}). More specifically, the global scope (`globalThis`) is composed of standard JavaScript features as usual, plus `window` as the prototype of the global scope. Most DOM APIs are inherit from the page through `window`, through [Xray vision](/en-US/docs/Mozilla/Add-ons/WebExtensions/Sharing_objects_with_page_scripts#xray_vision_in_firefox) to shield the content script from modifications by the web page. Content scripts may encounter JavaScript objects from its own global scope or Xray-wrapped versions from the web page. +- **In Firefox:** The global scope of the [content script environment](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts#content_script_environment) is not strictly equal to `window` ([Firefox bug 1208775](https://bugzil.la/1208775)). More specifically, the global scope (`globalThis`) is composed of standard JavaScript features as usual, plus `window` as the prototype of the global scope. Most DOM APIs are inherit from the page through `window`, through [Xray vision](/en-US/docs/Mozilla/Add-ons/WebExtensions/Sharing_objects_with_page_scripts#xray_vision_in_firefox) to shield the content script from modifications by the web page. Content scripts may encounter JavaScript objects from its own global scope or Xray-wrapped versions from the web page. - **In Chrome:** The global scope is `window` and the available DOM APIs are generally independent of the web page (other than sharing the underlying DOM). Content scripts cannot directly access JavaScript objects from the web page. #### Executing code in web page from content script @@ -210,11 +210,11 @@ When calling `tabs.remove()`: #### Sharing variables between content scripts -- **In Firefox:** You cannot share variables between content scripts by assigning them to `this.{variableName}` in one script and then attempting to access them using `window.{variableName}` in another. This is a limitation created by the sandbox environment in Firefox. This limitation may be removed, see {{bug(1208775)}}. +- **In Firefox:** You cannot share variables between content scripts by assigning them to `this.{variableName}` in one script and then attempting to access them using `window.{variableName}` in another. This is a limitation created by the sandbox environment in Firefox. This limitation may be removed, see [Firefox bug 1208775](https://bugzil.la/1208775). #### Content script lifecycle during navigation -- **In Firefox:** Content scripts remain injected in a web page after the user has navigated away, however, window object properties are destroyed. For example, if a content script sets `window.prop1 = "prop"` and the user then navigates away and returns to the page `window.prop1` is undefined. This issue is tracked in {{bug(1525400)}}. +- **In Firefox:** Content scripts remain injected in a web page after the user has navigated away, however, window object properties are destroyed. For example, if a content script sets `window.prop1 = "prop"` and the user then navigates away and returns to the page `window.prop1` is undefined. This issue is tracked in [Firefox bug 1525400](https://bugzil.la/1525400). To mimic the behavior of Chrome, listen for the [pageshow](/en-US/docs/Web/API/Window/pageshow_event) and [pagehide](/en-US/docs/Web/API/Window/pagehide_event) events. Then simulate the injection or destruction of the content script. @@ -262,7 +262,7 @@ These tables are generated from compatibility data stored as [JSON files in GitH Some extension APIs allow an extension to send data from one part of the extension to another, such as {{WebExtAPIRef("runtime.sendMessage()")}}, {{WebExtAPIRef("tabs.sendMessage()")}}, {{WebExtAPIRef("runtime.onMessage")}}, the `postMessage()` method of {{WebExtAPIRef("runtime.port")}}, and {{WebExtAPIRef("tabs.executeScript()")}}. - **In Firefox:** The [Structured clone algorithm](/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm) is used. -- **In Chrome:** The [JSON serialization algorithm](/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#description) is used. It may switch to structured cloning in the future ([issue 248548](https://bugs.chromium.org/p/chromium/issues/detail?id=248548)). +- **In Chrome:** The [JSON serialization algorithm](/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#description) is used. It may switch to structured cloning in the future ([issue 248548](https://crbug.com/248548)). The Structured clone algorithm supports more types than the JSON serialization algorithm. A notable exception are (DOM) objects with a `toJSON` method. DOM objects are not cloneable nor JSON-serializable by default, but with a `toJSON()` method, these can be JSON-serialized (but still not cloned with the structured cloning algorithm). Examples of JSON-serializable objects that are not structured cloneable include instances of {{domxref("URL")}} and {{domxref("PerformanceEntry")}}. diff --git a/files/en-us/mozilla/add-ons/webextensions/content_scripts/index.md b/files/en-us/mozilla/add-ons/webextensions/content_scripts/index.md index 0680b88309534a6..eee844eae97bf74 100644 --- a/files/en-us/mozilla/add-ons/webextensions/content_scripts/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/content_scripts/index.md @@ -54,8 +54,8 @@ Using methods (1) and (2), you can only load scripts into pages whose URLs can b Using method (3), you can also load scripts into pages packaged with your extension, but you can't load scripts into privileged browser pages (like "`about:debugging`" or "`about:addons`"). -> **Note:** [Dynamic JS module imports](/en-US/docs/Web/JavaScript/Guide/Modules#dynamic_module_loading) are now working in content scripts. For more details, see {{bug(1536094)}}. -> Only URLs with the _moz-extension_ scheme are allowed, which excludes data URLs ({{bug(1587336)}}). +> **Note:** [Dynamic JS module imports](/en-US/docs/Web/JavaScript/Guide/Modules#dynamic_module_loading) are now working in content scripts. For more details, see [Firefox bug 1536094](https://bugzil.la/1536094). +> Only URLs with the _moz-extension_ scheme are allowed, which excludes data URLs ([Firefox bug 1587336](https://bugzil.la/1587336)). ## Content script environment diff --git a/files/en-us/mozilla/add-ons/webextensions/content_security_policy/index.md b/files/en-us/mozilla/add-ons/webextensions/content_security_policy/index.md index 396dec9671b127c..48287455d33991e 100644 --- a/files/en-us/mozilla/add-ons/webextensions/content_security_policy/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/content_security_policy/index.md @@ -117,7 +117,7 @@ Extensions wishing to use [WebAssembly](/en-US/docs/WebAssembly) require `'wasm- From Firefox 102 and Chrome 103, `'wasm-unsafe-eval'` can be included in the [`content_security_policy`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy) manifest.json key to enable the use of WebAssembly in extensions. -Manifest V2 extensions in Firefox can use WebAssembly without `'wasm-unsafe-eval'` in their CSP for backward compatibility. However, this behavior isn't guaranteed, see {{bug(1770909)}}. Extensions using WebAssembly are therefore encouraged to declare `'wasm-unsafe-eval'` in their CSP. +Manifest V2 extensions in Firefox can use WebAssembly without `'wasm-unsafe-eval'` in their CSP for backward compatibility. However, this behavior isn't guaranteed, see [Firefox bug 1770909](https://bugzil.la/1770909). Extensions using WebAssembly are therefore encouraged to declare `'wasm-unsafe-eval'` in their CSP. For Chrome, extensions cannot use WebAssembly in version 101 or earlier. In 102, extensions can use WebAssembly (the same behavior as Firefox 101 and earlier). From version 103, extensions can use WebAssembly if they include `'wasm-unsafe-eval'` in the `content_security_policy` in the manifest key. @@ -132,8 +132,8 @@ Manifest V3 Extensions that need to make `http:` or `ws:` requests can opt out o ## CSP for content scripts In Manifest V2, content scripts have no CSP. -As of Manifest V3, content scripts share the default CSP as extensions. It is currently not possible to specify a separate CSP for content scripts ([source](https://bugzilla.mozilla.org/show_bug.cgi?id=1581611#c10)). +As of Manifest V3, content scripts share the default CSP as extensions. It is currently not possible to specify a separate CSP for content scripts ([source](https://bugzil.la/1581611#c10)). The extent to which the CSP controls loads from content scripts varies by browser. In Firefox, JavaScript features such as eval are restricted by the extension CSP. Generally, most DOM-based APIs are subjected to the CSP of the web page. -In Chrome, many DOM APIs are covered by the extension CSP instead of the web page's CSP ([crbug 896041](https://bugs.chromium.org/p/chromium/issues/detail?id=896041)). +In Chrome, many DOM APIs are covered by the extension CSP instead of the web page's CSP ([crbug 896041](https://crbug.com/896041)). diff --git a/files/en-us/mozilla/add-ons/webextensions/implement_a_settings_page/index.md b/files/en-us/mozilla/add-ons/webextensions/implement_a_settings_page/index.md index 270e6be051fa566..f63a5a0fa1a9169 100644 --- a/files/en-us/mozilla/add-ons/webextensions/implement_a_settings_page/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/implement_a_settings_page/index.md @@ -155,7 +155,7 @@ This does two things: You could store the settings values in local storage instead if you feel that local storage is preferable for your extension. -> **Note:** The implementation of `storage.sync` in Firefox relies on the Add-on ID. If you use `storage.sync`, you must set an ID for your extension using the [`browser_specific_settings`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings) key in `manifest.json`, as shown in the example manifest above. See {{bug(1323228)}} for related information. +> **Note:** The implementation of `storage.sync` in Firefox relies on the Add-on ID. If you use `storage.sync`, you must set an ID for your extension using the [`browser_specific_settings`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings) key in `manifest.json`, as shown in the example manifest above. See [Firefox bug 1323228](https://bugzil.la/1323228) for related information. Finally, update `borderify.js` to read the border color from storage: diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_security_policy/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_security_policy/index.md index ebd285cd605f717..e1bff012b5d77c8 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_security_policy/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_security_policy/index.md @@ -209,7 +209,7 @@ Enable the use of [WebAssembly](/en-US/docs/WebAssembly): - Manifest V2 - For backward compatibility, Manifest V2 extensions in Firefox can use WebAssembly without the use of `'wasm-unsafe-eval'`. However, this behavior isn't guaranteed. See {{bug(1770909)}}. Extensions using WebAssembly are therefore encouraged to declare `'wasm-unsafe-eval'` in their CSP. See [WebAssembly](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy#webassembly) on the Content Security Policy page for more information. + For backward compatibility, Manifest V2 extensions in Firefox can use WebAssembly without the use of `'wasm-unsafe-eval'`. However, this behavior isn't guaranteed. See [Firefox bug 1770909](https://bugzil.la/1770909). Extensions using WebAssembly are therefore encouraged to declare `'wasm-unsafe-eval'` in their CSP. See [WebAssembly](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy#webassembly) on the Content Security Policy page for more information. ```json "content_security_policy": "script-src 'self' 'wasm-unsafe-eval'" diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/externally_connectable/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/externally_connectable/index.md index c10809f5e516452..c404a38a5dcfc32 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/externally_connectable/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/externally_connectable/index.md @@ -53,7 +53,7 @@ Externally connectable controls which other extensions and web pages can communi > > - In Chrome, `chrome.runtime.connect` and `chrome.runtime.sendMessage` are used. These methods are only available when there is at least one extension listening for messages, see [chrome.runtime will no longer be defined unconditionally in Chrome 106](https://groups.google.com/a/chromium.org/g/chromium-extensions/c/tCWVZRq77cg/m/KB6-tvCdAgAJ) for more details. > - In Safari, `browser.runtime.connect` and `browser.runtime.sendMessage` are used. -> - In Firefox, neither API is supported. See {{bug(1319168)}}. +> - In Firefox, neither API is supported. See [Firefox bug 1319168](https://bugzil.la/1319168). ### "ids" attribute diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/icons/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/icons/index.md index 36a6a510f67340b..fb45f3ee8a8df92 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/icons/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/icons/index.md @@ -85,7 +85,7 @@ You can use SVG and the browser will scale your icon appropriately. There are cu } ``` -> **Note:** Only Firefox is known to support SVG icons. Chromium has a bug about [unsupported SVG icons](https://bugs.chromium.org/p/chromium/issues/detail?id=29683). +> **Note:** Only Firefox is known to support SVG icons. Chromium has a bug about [unsupported SVG icons](https://crbug.com/29683). > **Note:** Remember to include the `xmlns` attribute when creating the SVG. Otherwise, Firefox won't be able to display the icon. diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/optional_permissions/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/optional_permissions/index.md index eb6e8e9d8931073..faa72faff356cf7 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/optional_permissions/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/optional_permissions/index.md @@ -56,7 +56,7 @@ These are the same as the host permissions you can specify in the [`permissions` > **Note:** When using Manifest V3 or higher: > > - in Chrome, host permissions must be specified in the [`host_permission`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/host_permissions) manifest key. -> - in Firefox, during the Manifest V3 developer preview, hosts can be in either `host_permissions` or `optional_permissions`. Subject to completion of [bug 1766026](https://bugzilla.mozilla.org/show_bug.cgi?id=1766026), hosts will be specified in either `host_permissions` or `optional_host_permissions`. +> - in Firefox, during the Manifest V3 developer preview, hosts can be in either `host_permissions` or `optional_permissions`. Subject to completion of [bug 1766026](https://bugzil.la/1766026), hosts will be specified in either `host_permissions` or `optional_host_permissions`. ## API permissions diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/permissions/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/permissions/index.md index 057e2db15212b67..9fcabf81687fe18 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/permissions/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/permissions/index.md @@ -170,7 +170,7 @@ For example, consider an extension that wants to run a script in the current pag Usually the tab that's granted `activeTab` is just the currently active tab, except in one case. The {{webextAPIref("menus")}} API enables an extension to create a menu item which is shown if the user context-clicks on a tab (that is, on the element in the tabstrip that enables the user to switch from one tab to another). -If the user clicks such an item, then the `activeTab` permission is granted for the tab the user clicked, even if it's not the currently active tab (as of Firefox 63, {{bug(1446956)}}). +If the user clicks such an item, then the `activeTab` permission is granted for the tab the user clicked, even if it's not the currently active tab (as of Firefox 63, [Firefox bug 1446956](https://bugzil.la/1446956)). ## Clipboard access diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/theme/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/theme/index.md index 0e2b1e764fd76fd..6951c7faf19a443 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/theme/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/theme/index.md @@ -54,7 +54,7 @@ Use the theme key to define a static theme to apply to Firefox. > **Note:** If you want to include a theme with an extension, please see the {{WebExtAPIRef("theme")}} API. -> **Note:** Since May 2019, themes need to be signed to be installed ({{bug(1545109)}}). See [Signing and distributing your add-on](https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/#distributing-your-addon) for more details. +> **Note:** Since May 2019, themes need to be signed to be installed ([Firefox bug 1545109](https://bugzil.la/1545109)). See [Signing and distributing your add-on](https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/#distributing-your-addon) for more details. > **Note:** A new version of Firefox for Android, based on GeckoView, is under development. A [pre-release version](https://play.google.com/store/apps/details?id=org.mozilla.fenix) is available. The pre-release version does not support themes. @@ -158,7 +158,7 @@ Images should be 200 pixels high to ensure they always fill the header space ver before Firefox 60. Note also that in Firefox 60 onwards, any {{cssxref("text-shadow")}} applied to the header text is removed if no headerURL is specified (see - {{bug(1404688)}}). + [Firefox bug 1404688](https://bugzil.la/1404688)).

In Firefox for Android, headerURL or diff --git a/files/en-us/mozilla/add-ons/webextensions/user_interface/browser_styles/index.md b/files/en-us/mozilla/add-ons/webextensions/user_interface/browser_styles/index.md index 04a9e55af92d7fe..ef0132b702f8e4f 100644 --- a/files/en-us/mozilla/add-ons/webextensions/user_interface/browser_styles/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/user_interface/browser_styles/index.md @@ -114,7 +114,7 @@ Most styles are automatically applied, but some elements require you to add the -> **Note:** See {{bug(1465256)}} for removal of this unnecessary requirement. +> **Note:** See [Firefox bug 1465256](https://bugzil.la/1465256) for removal of this unnecessary requirement. ## Browser compatibility diff --git a/files/en-us/mozilla/add-ons/webextensions/user_interface/popups/index.md b/files/en-us/mozilla/add-ons/webextensions/user_interface/popups/index.md index 056a3b96b90187f..c0dead6f0e80d0a 100644 --- a/files/en-us/mozilla/add-ons/webextensions/user_interface/popups/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/user_interface/popups/index.md @@ -47,7 +47,7 @@ You can debug a popup's markup and JavaScript using the Add-on Debugger, but you Popups resize automatically to fit their content. The algorithm for this may differ from one browser to another. -In Firefox, the size is calculated just before the popup is shown, and at most 10 times per second after DOM mutations. For strict mode documents, the size is calculated based on the layout size of the [``](/en-US/docs/Web/HTML/Element/body) element. For quirks mode, it's the [``](/en-US/docs/Web/HTML/Element/html) element. Firefox calculates the preferred width of the contents of that element, reflows it to that width, and then resizes so there's no vertical scrolling. It will grow to a size of **800x600 pixels** at most if that fits on the user's screen. (Prior to Firefox 60 [it was only 680px](https://bugzilla.mozilla.org/show_bug.cgi?id=1434177).) If the user [moves the extension's button to the menu](https://support.mozilla.org/en-US/kb/customize-firefox-controls-buttons-and-toolbars#w_customize-the-menu-or-the-toolbar) or it appears in the toolbar overflow, then the popup appears inside the menu's panel and is given a fixed width. +In Firefox, the size is calculated just before the popup is shown, and at most 10 times per second after DOM mutations. For strict mode documents, the size is calculated based on the layout size of the [``](/en-US/docs/Web/HTML/Element/body) element. For quirks mode, it's the [``](/en-US/docs/Web/HTML/Element/html) element. Firefox calculates the preferred width of the contents of that element, reflows it to that width, and then resizes so there's no vertical scrolling. It will grow to a size of **800x600 pixels** at most if that fits on the user's screen. (Prior to Firefox 60 [it was only 680px](https://bugzil.la/1434177).) If the user [moves the extension's button to the menu](https://support.mozilla.org/en-US/kb/customize-firefox-controls-buttons-and-toolbars#w_customize-the-menu-or-the-toolbar) or it appears in the toolbar overflow, then the popup appears inside the menu's panel and is given a fixed width. When setting the popup `width` in CSS, you should set the it in the [``](/en-US/docs/Web/HTML/Element/body) and not in the `:root`. diff --git a/files/en-us/mozilla/firefox/experimental_features/index.md b/files/en-us/mozilla/firefox/experimental_features/index.md index 234882881b9d721..e568047a105bf95 100644 --- a/files/en-us/mozilla/firefox/experimental_features/index.md +++ b/files/en-us/mozilla/firefox/experimental_features/index.md @@ -20,7 +20,7 @@ Experimental features can be enabled or disabled using the [Firefox Configuratio ### inert attribute -The {{domxref("HTMLElement")}} property {{DOMxRef("HTMLElement.inert")}} is a {{jsxref("Boolean")}}. When present, it may make the browser "ignore" the element from assistive technologies, page search, and text selection. For more details on the status of this feature, see {{bug(1655722)}}. +The {{domxref("HTMLElement")}} property {{DOMxRef("HTMLElement.inert")}} is a {{jsxref("Boolean")}}. When present, it may make the browser "ignore" the element from assistive technologies, page search, and text selection. For more details on the status of this feature, see [Firefox bug 1655722](https://bugzil.la/1655722). @@ -60,7 +60,7 @@ The {{domxref("HTMLElement")}} property {{DOMxRef("HTMLElement.inert")}} is a {{ ### Layout for input type="search" -Layout for `input type="search"` has been updated. This causes a search field to have a clear icon once someone starts typing in it, to match other browser implementations. (See {{bug(558594)}} for more details.) +Layout for `input type="search"` has been updated. This causes a search field to have a clear icon once someone starts typing in it, to match other browser implementations. (See [Firefox bug 558594](https://bugzil.la/558594) for more details.)
@@ -100,7 +100,7 @@ Layout for `input type="search"` has been updated. This causes a search field to ### Toggle password display -HTML password input elements ([``](/en-US/docs/Web/HTML/Element/input/password)) include an "eye" icon that can be toggled to display or obscure the password text ({{bug(502258)}}). +HTML password input elements ([``](/en-US/docs/Web/HTML/Element/input/password)) include an "eye" icon that can be toggled to display or obscure the password text ([Firefox bug 502258](https://bugzil.la/502258)).
@@ -142,7 +142,7 @@ HTML password input elements ([``](/en-US/docs/Web/HTML/E ### Hex boxes to display stray control characters -This feature renders control characters (Unicode category Cc) other than _tab_ (`U+0009`), _line feed_ (`U+000A`), _form feed_ (`U+000C`), and _carriage return_ (`U+000D`) as a hexbox when they are not expected. (See {{bug(1099557)}} for more details.) +This feature renders control characters (Unicode category Cc) other than _tab_ (`U+0009`), _line feed_ (`U+000A`), _form feed_ (`U+000C`), and _carriage return_ (`U+000D`) as a hexbox when they are not expected. (See [Firefox bug 1099557](https://bugzil.la/1099557) for more details.)
@@ -185,7 +185,7 @@ This feature renders control characters (Unicode category Cc) other than _tab_ ( ### initial-letter property -The {{cssxref("initial-letter")}} CSS property is part of the [CSS Inline Layout](https://drafts.csswg.org/css-inline/) specification and allows you to specify how dropped, raised, and sunken initial letters are displayed. (See {{bug(1223880)}} for more details.) +The {{cssxref("initial-letter")}} CSS property is part of the [CSS Inline Layout](https://drafts.csswg.org/css-inline/) specification and allows you to specify how dropped, raised, and sunken initial letters are displayed. (See [Firefox bug 1223880](https://bugzil.la/1223880) for more details.)
@@ -226,7 +226,7 @@ The {{cssxref("initial-letter")}} CSS property is part of the [CSS Inline Layout ### content-visibility: auto value The [`content-visibility`](/en-US/docs/Web/CSS/content-visibility) CSS property value `auto` allows content to skip rendering if it is not [relevant to the user](/en-US/docs/Web/CSS/CSS_Containment#relevant_to_the_user). -(See {{bug(1798485)}} for more details.) +(See [Firefox bug 1798485](https://bugzil.la/1798485) for more details.)
@@ -266,11 +266,11 @@ The [`content-visibility`](/en-US/docs/Web/CSS/content-visibility) CSS property Note that the related {{domxref("element/contentvisibilityautostatechange_event", "contentvisibilityautostatechange")}} event and associated {{domxref("ContentVisibilityAutoStateChangeEvent")}} interface were added in version 110, and are gated by the same preference. These can be used by application code to monitor visibility changes and stop processes related to rendering the element when the user agent is [skipping its contents](/en-US/docs/Web/CSS/CSS_Containment#skips_its_contents). -(See {{bug(1791759)}} for more details.) +(See [Firefox bug 1791759](https://bugzil.la/1791759) for more details.) ### Single numbers as aspect ratio in media queries -Support for using a single {{cssxref("number")}} as a {{cssxref("ratio")}} when specifying the aspect ratio for a [media query](/en-US/docs/Web/CSS/Media_Queries). (See {{bug(1565562)}} for more details.) +Support for using a single {{cssxref("number")}} as a {{cssxref("ratio")}} when specifying the aspect ratio for a [media query](/en-US/docs/Web/CSS/Media_Queries). (See [Firefox bug 1565562](https://bugzil.la/1565562) for more details.)
@@ -310,7 +310,7 @@ Support for using a single {{cssxref("number")}} as a {{cssxref("ratio")}} when ### backdrop-filter property -The {{cssxref("backdrop-filter")}} property applies filter effects to the area behind an element. (See {{bug(1178765)}} for more details.) +The {{cssxref("backdrop-filter")}} property applies filter effects to the area behind an element. (See [Firefox bug 1178765](https://bugzil.la/1178765) for more details.)
@@ -350,7 +350,7 @@ The {{cssxref("backdrop-filter")}} property applies filter effects to the area b ### Masonry grid layout -Adds support for a [masonry-style layout](/en-US/docs/Web/CSS/CSS_Grid_Layout/Masonry_Layout) based on grid layout where one axis has a masonry layout and the other has a normal grid layout. This allows developers to easily create gallery style layouts like on Pinterest. See {{bug(1607954)}} for more details. +Adds support for a [masonry-style layout](/en-US/docs/Web/CSS/CSS_Grid_Layout/Masonry_Layout) based on grid layout where one axis has a masonry layout and the other has a normal grid layout. This allows developers to easily create gallery style layouts like on Pinterest. See [Firefox bug 1607954](https://bugzil.la/1607954) for more details.
@@ -392,7 +392,7 @@ Adds support for a [masonry-style layout](/en-US/docs/Web/CSS/CSS_Grid_Layout/Ma ### math-style property -The {{cssxref("math-style")}} property indicates whether MathML equations should render with normal or compact height. (See {{bug(1665975)}} for more details.) +The {{cssxref("math-style")}} property indicates whether MathML equations should render with normal or compact height. (See [Firefox bug 1665975](https://bugzil.la/1665975) for more details.)
@@ -432,7 +432,7 @@ The {{cssxref("math-style")}} property indicates whether MathML equations should ### fit-content() function -The {{cssxref("fit-content_function", "fit-content()")}} function as it applies to {{cssxref("width")}} and other sizing properties. This function is already well-supported for CSS Grid Layout track sizing. (See {{bug(1312588)}} for more details.) +The {{cssxref("fit-content_function", "fit-content()")}} function as it applies to {{cssxref("width")}} and other sizing properties. This function is already well-supported for CSS Grid Layout track sizing. (See [Firefox bug 1312588](https://bugzil.la/1312588) for more details.)
@@ -477,7 +477,7 @@ The {{cssxref('scroll-timeline-name')}} and {{cssxref('scroll-timeline-axis')}} The scroll timeline can then be associated with an [animation](/en-US/docs/Web/CSS/CSS_Animations) by setting the {{cssxref('animation-timeline')}} property to the name value that was set in `scroll-timeline-name`. You can alternatively use the [`scroll()`](/en-US/docs/Web/CSS/animation-timeline/scroll) functional notation with {{cssxref('animation-timeline')}} to indicate that a scrollbar axis in an ancestor element will be used for the timeline. -For more information, see {{bug(1676791)}}, {{bug(1754897)}}, and {{bug(1737918)}}. +For more information, see [Firefox bug 1676791](https://bugzil.la/1676791), [Firefox bug 1754897](https://bugzil.la/1754897), and [Firefox bug 1737918](https://bugzil.la/1737918).
@@ -518,7 +518,7 @@ For more information, see {{bug(1676791)}}, {{bug(1754897)}}, and {{bug(1737918) ### :has() pseudo-class The [`:has()`](/en-US/docs/Web/CSS/:has) pseudo-class selects elements that contain the selectors passed as parameters. -(See {{bug(1771896)}} for more details.) +(See [Firefox bug 1771896](https://bugzil.la/1771896) for more details.)
@@ -559,7 +559,7 @@ The [`:has()`](/en-US/docs/Web/CSS/:has) pseudo-class selects elements that cont ### linear() easing function The `linear()` [easing function](/en-US/docs/Web/CSS/easing-function) defines a piecewise linear function, allowing you to approximate more complex animations. -(See {{bug(1764126)}} for more details.) +(See [Firefox bug 1764126](https://bugzil.la/1764126) for more details.)
@@ -600,7 +600,7 @@ The `linear()` [easing function](/en-US/docs/Web/CSS/easing-function) defines a ### animation-composition property The [`animation-composition`](/en-US/docs/Web/CSS/animation-composition) property specifies the composite operation to perform when multiple animations affect the same property simultaneously. -(See {{bug(1293490)}} for more details.) +(See [Firefox bug 1293490](https://bugzil.la/1293490) for more details.)
@@ -641,7 +641,7 @@ The [`animation-composition`](/en-US/docs/Web/CSS/animation-composition) propert ### @font-face src feature checking The `@font-face` [`src` descriptor](/en-US/docs/Web/CSS/@font-face/src) now supports the `tech()` function, allowing fallback of whether a font resource is downloaded based on whether the user-agent supports a particular font feature or technology. -See {{bug(1715546)}} for more details. +See [Firefox bug 1715546](https://bugzil.la/1715546) for more details.
@@ -682,7 +682,7 @@ See {{bug(1715546)}} for more details. ### round() math function The CSS [`round()`](/en-US/docs/Web/CSS/round) function is a math function that rounds a number (or the result of an expression) based on a selected rounding strategy. -See {{bug(1764850)}} for more details. +See [Firefox bug 1764850](https://bugzil.la/1764850) for more details.
@@ -723,7 +723,7 @@ See {{bug(1764850)}} for more details. ### font-variant-emoji The CSS [`font-variant-emoji`](/en-US/docs/Web/CSS/font-variant-emoji) property allows you to set a default presentation style for displaying emojis. -See ({{bug(1461589)}}) for more details. +See ([Firefox bug 1461589](https://bugzil.la/1461589)) for more details.
@@ -767,7 +767,7 @@ See ({{bug(1461589)}}) for more details. The SVGPathSeg APIs are being unshipped, and have been placed behind a preference. This includes: `SVGPathSegList`, [SVGPathElement.getPathSegAtLength()](/en-US/docs/Web/API/SVGPathElement), `SVGAnimatedPathData`. -(See {{bug(1388931)}} for more details.) +(See [Firefox bug 1388931](https://bugzil.la/1388931) for more details.)
@@ -811,7 +811,7 @@ This includes: `SVGPathSegList`, [SVGPathElement.getPathSegAtLength()](/en-US/do The {{jsxref("Array.prototype.group()")}} and {{jsxref("Array.prototype.groupToMap()")}} methods are used to group the elements of an array using a string or value, respectively, returned by a test function. The `groupBy` method should be used when strings can be used to represent element groups, while `groupByToMap()` should be used in cases where it makes sense to use a value as the key. -(See {{bug(1739648)}} for more details.) +(See [Firefox bug 1739648](https://bugzil.la/1739648) for more details.)
@@ -855,7 +855,7 @@ The `groupBy` method should be used when strings can be used to represent elemen #### Interface: OffscreenCanvas -The {{domxref("OffscreenCanvas")}} interface provides a canvas that can be rendered offscreen. It is available in both the window and [worker](/en-US/docs/Web/API/Web_Workers_API) contexts. (See {{bug(1390089)}} for more details.) +The {{domxref("OffscreenCanvas")}} interface provides a canvas that can be rendered offscreen. It is available in both the window and [worker](/en-US/docs/Web/API/Web_Workers_API) contexts. (See [Firefox bug 1390089](https://bugzil.la/1390089) for more details.)
@@ -939,7 +939,7 @@ When this preference is enabled, any WebGL extensions currently in "draft" statu #### WebGPU API -This new API provides low-level support for performing computation and graphics rendering using the [Graphics Processing Unit](https://en.wikipedia.org/wiki/Graphics_Processing_Unit) (GPU) of the user's device or computer. The [specification](https://gpuweb.github.io/gpuweb/) is still a work-in-progress. See {{bug(1602129)}} for our progress on this API. +This new API provides low-level support for performing computation and graphics rendering using the [Graphics Processing Unit](https://en.wikipedia.org/wiki/Graphics_Processing_Unit) (GPU) of the user's device or computer. The [specification](https://gpuweb.github.io/gpuweb/) is still a work-in-progress. See [Firefox bug 1602129](https://bugzil.la/1602129) for our progress on this API.
@@ -981,7 +981,7 @@ This new API provides low-level support for performing computation and graphics #### MediaDevices.selectAudioOutput() -{{domxref("MediaDevices.selectAudioOutput()")}} displays a prompt on desktop systems, from which users can select their desired audio output. See {{bug(1699026)}}. +{{domxref("MediaDevices.selectAudioOutput()")}} displays a prompt on desktop systems, from which users can select their desired audio output. See [Firefox bug 1699026](https://bugzil.la/1699026).
@@ -1025,7 +1025,7 @@ The following experimental features include those found in the [WebRTC API](/en- #### Asynchronous SourceBuffer add and remove -This adds the promise-based methods {{domxref("SourceBuffer.appendBufferAsync", "appendBufferAsync()")}} and {{domxref("SourceBuffer.removeAsync", "removeAsync()")}} for adding and removing media source buffers to the {{domxref("SourceBuffer")}} interface. See {{bug(1280613)}} and {{bug(778617)}} for more information. +This adds the promise-based methods {{domxref("SourceBuffer.appendBufferAsync", "appendBufferAsync()")}} and {{domxref("SourceBuffer.removeAsync", "removeAsync()")}} for adding and removing media source buffers to the {{domxref("SourceBuffer")}} interface. See [Firefox bug 1280613](https://bugzil.la/1280613) and [Firefox bug 778617](https://bugzil.la/778617) for more information.
@@ -1152,7 +1152,7 @@ This feature allows Firefox on Android to use [AV1 format media](/en-US/docs/Web #### JPEG XL support -With this feature enabled, Firefox supports [JPEG XL](https://jpeg.org/jpegxl/) images, see {{bug(1539075)}} for more details. +With this feature enabled, Firefox supports [JPEG XL](https://jpeg.org/jpegxl/) images, see [Firefox bug 1539075](https://bugzil.la/1539075) for more details.
@@ -1194,7 +1194,7 @@ With this feature enabled, Firefox supports [JPEG XL](https://jpeg.org/jpegxl/) This feature provides support for the [OpenFont COLRv1 font specification](https://docs.microsoft.com/en-us/typography/opentype/spec/). This enables compression-friendly color vector fonts with gradients, compositing and blending to be loaded using the CSS [`@font-face`](/en-US/docs/Web/CSS/@font-face) rule, or the [CSS Font Loading API](/en-US/docs/Web/API/CSS_Font_Loading_API). -See {{bug(1740530)}} for more details. +See [Firefox bug 1740530](https://bugzil.la/1740530) for more details.
@@ -1280,7 +1280,7 @@ Preloading occurs in parallel with worker bootup, reducing the total time from s #### WebVR API (Disabled) The deprecated [WebVR API](/en-US/docs/Web/API/WebVR_API) is on the path for removal. -It is disabled by default on all builds {{bug(1750902)}}. +It is disabled by default on all builds [Firefox bug 1750902](https://bugzil.la/1750902).
@@ -1322,7 +1322,7 @@ It is disabled by default on all builds {{bug(1750902)}}. #### HTMLMediaElement method: setSinkId() -{{domxref("HTMLMediaElement.setSinkId()")}} allows you to set the sink ID of an audio output device on an {{domxref("HTMLMediaElement")}}, thereby changing where the audio is being output. See {{bug(934425)}} for more details. +{{domxref("HTMLMediaElement.setSinkId()")}} allows you to set the sink ID of an audio output device on an {{domxref("HTMLMediaElement")}}, thereby changing where the audio is being output. See [Firefox bug 934425](https://bugzil.la/934425) for more details.
@@ -1362,7 +1362,7 @@ It is disabled by default on all builds {{bug(1750902)}}. #### HTMLMediaElement properties: audioTracks and videoTracks -Enabling this feature adds the {{domxref("HTMLMediaElement.audioTracks")}} and {{domxref("HTMLMediaElement.videoTracks")}} properties to all HTML media elements. However, because Firefox doesn't currently support multiple audio and video tracks, the most common use cases for these properties don't work, so they're both disabled by default. See {{bug(1057233)}} for more details. +Enabling this feature adds the {{domxref("HTMLMediaElement.audioTracks")}} and {{domxref("HTMLMediaElement.videoTracks")}} properties to all HTML media elements. However, because Firefox doesn't currently support multiple audio and video tracks, the most common use cases for these properties don't work, so they're both disabled by default. See [Firefox bug 1057233](https://bugzil.la/1057233) for more details.
@@ -1442,7 +1442,7 @@ The {{domxref('ClipboardItem')}} interface of the {{domxref('Clipboard API')}} i #### ClipboardRead -The [Clipboard.read()](/en-US/docs/Web/API/Clipboard/read) method of the {{domxref('Clipboard')}} interface is also now available under the `dom.events.asyncClipboard.read` preference, when previously it was under `dom.events.asyncClipboard.clipboardItem`. (See {{bug(1701512)}} for more details.) +The [Clipboard.read()](/en-US/docs/Web/API/Clipboard/read) method of the {{domxref('Clipboard')}} interface is also now available under the `dom.events.asyncClipboard.read` preference, when previously it was under `dom.events.asyncClipboard.clipboardItem`. (See [Firefox bug 1701512](https://bugzil.la/1701512) for more details.)
@@ -1525,7 +1525,7 @@ The {{domxref('HTML Sanitizer API')}} allow developers to take untrusted strings The {{domxref("navigator.getAutoplayPolicy()")}} method returns a string value indicating how the browser handles requests to automatically play media for either media elements or audio contexts. The possible values are: `allowed` (autoplay is currently permitted), `allowed-muted` (autoplay is allowed but only with no—or muted—audio), and `disallowed` (autoplay is not allowed at this time). The value can change over time for all items of a particular type, or for a particular item, depending on what the user is doing, their preferences, and the state of the browser in general. -See {{bug(1773551)}} for more details. +See [Firefox bug 1773551](https://bugzil.la/1773551) for more details.
@@ -1565,7 +1565,7 @@ See {{bug(1773551)}} for more details. #### GeometryUtils methods: convertPointFromNode(), convertRectFromNode(), and convertQuadFromNode() -The `GeometryUtils` methods `convertPointFromNode()`, `convertRectFromNode()`, and `convertQuadFromNode()` map the given point, rectangle, or quadruple from the {{domxref("Node")}} on which they're called to another node. (See {{bug(918189)}} for more details.) +The `GeometryUtils` methods `convertPointFromNode()`, `convertRectFromNode()`, and `convertQuadFromNode()` map the given point, rectangle, or quadruple from the {{domxref("Node")}} on which they're called to another node. (See [Firefox bug 918189](https://bugzil.la/918189) for more details.)
@@ -1605,7 +1605,7 @@ The `GeometryUtils` methods `convertPointFromNode()`, `convertRectFromNode()`, a #### GeometryUtils method: getBoxQuads() -The `GeometryUtils` method `getBoxQuads()` returns the CSS boxes for a {{domxref("Node")}} relative to any other node or viewport. (See {{bug(917755)}} for more details.) +The `GeometryUtils` method `getBoxQuads()` returns the CSS boxes for a {{domxref("Node")}} relative to any other node or viewport. (See [Firefox bug 917755](https://bugzil.la/917755) for more details.)
@@ -1652,7 +1652,7 @@ New {{domxref("ElementInternals")}} properties and methods that allow custom ele - The {{domxref("ElementInternals.willValidate", "willValidate")}} property checks if a custom form element will be validated. - The {{domxref("ElementInternals.setFormValue()","setFormValue()")}} method sets the sanitized value and user-entered data, if needed. -See these bugs for details: {{bug(1556362)}}, {{bug(1556373)}}, {{bug(1556365)}}, {{bug(1556449)}}. +See these bugs for details: [Firefox bug 1556362](https://bugzil.la/1556362), [Firefox bug 1556373](https://bugzil.la/1556373), [Firefox bug 1556365](https://bugzil.la/1556365), [Firefox bug 1556449](https://bugzil.la/1556449).
@@ -1694,7 +1694,7 @@ See these bugs for details: {{bug(1556362)}}, {{bug(1556373)}}, {{bug(1556365)}} #### Primary payment handling -The [Payment Request API](/en-US/docs/Web/API/Payment_Request_API) provides support for handling web-based payments within web content or apps. Due to a bug that came up during testing of the user interface, we have decided to postpone shipping this API while discussions over potential changes to the API are held. Work is ongoing. (See {{bug(1318984)}} for more details.) +The [Payment Request API](/en-US/docs/Web/API/Payment_Request_API) provides support for handling web-based payments within web content or apps. Due to a bug that came up during testing of the user interface, we have decided to postpone shipping this API while discussions over potential changes to the API are held. Work is ongoing. (See [Firefox bug 1318984](https://bugzil.la/1318984) for more details.)
@@ -1783,7 +1783,7 @@ This feature is enabled on Android in all builds, but behind a preference on Des The {{domxref("ScreenOrientation.lock()")}} method allows a device to be locked to a particular orientation, if supported by the device and allowed by browser pre-lock requirements. Typically locking the orientation is only allowed on mobile devices when the document is being displayed full screen. -See {{bug(1697647)}} for more details. +See [Firefox bug 1697647](https://bugzil.la/1697647) for more details. Note that since locking the screen orientation isn't typically supported on desktop systems, you will need to use Firefox for Android Nightly build and enable the preference in `about:config`. @@ -1834,7 +1834,7 @@ No preference is provided to allow it to be enabled in other releases. ### Block plain text requests from Flash on encrypted pages -In order to help mitigate man-in-the-middle (MitM) attacks caused by Flash content on encrypted pages, a preference has been added to treat `OBJECT_SUBREQUEST`s as active content. See {{bug(1190623)}} for more details. +In order to help mitigate man-in-the-middle (MitM) attacks caused by Flash content on encrypted pages, a preference has been added to treat `OBJECT_SUBREQUEST`s as active content. See [Firefox bug 1190623](https://bugzil.la/1190623) for more details.
@@ -1876,7 +1876,7 @@ In order to help mitigate man-in-the-middle (MitM) attacks caused by Flash conte ### Insecure page labeling -These two preferences add a "Not secure" text label in the address bar next to the traditional lock icon when a page is loaded insecurely (that is, using {{Glossary("HTTP")}} rather than {{Glossary("HTTPS")}}). See {{bug(1335970)}} for more details. +These two preferences add a "Not secure" text label in the address bar next to the traditional lock icon when a page is loaded insecurely (that is, using {{Glossary("HTTP")}} rather than {{Glossary("HTTPS")}}). See [Firefox bug 1335970](https://bugzil.la/1335970) for more details.
@@ -1921,7 +1921,7 @@ These two preferences add a "Not secure" text label in the address bar next to t ### Upgrading mixed display content -When enabled, this preference causes Firefox to automatically upgrade requests for media content from HTTP to HTTPS on secure pages. The intent is to prevent mixed-content conditions in which some content is loaded securely while other content is insecure. If the upgrade fails (because the media's host doesn't support HTTPS), the media is not loaded. (See {{bug(1435733)}} for more details.) +When enabled, this preference causes Firefox to automatically upgrade requests for media content from HTTP to HTTPS on secure pages. The intent is to prevent mixed-content conditions in which some content is loaded securely while other content is insecure. If the upgrade fails (because the media's host doesn't support HTTPS), the media is not loaded. (See [Firefox bug 1435733](https://bugzil.la/1435733) for more details.) This also changes the console warning; if the upgrade succeeds, the message indicates that the request was upgraded, instead of showing a warning. @@ -2010,7 +2010,7 @@ Note that this is implemented in Firefox as "**Feature Policy**, the name used i The [`Clear-Site-Data`](/en-US/docs/Web/HTTP/Headers/Clear-Site-Data) HTTP response header `cache` directive clears the browser cache for the requesting website. -> **Note:** This was originally enabled by default, but put behind a preference in version 94 ({{bug(1729291)}}). +> **Note:** This was originally enabled by default, but put behind a preference in version 94 ([Firefox bug 1729291](https://bugzil.la/1729291)).
@@ -2056,7 +2056,7 @@ Mozilla's developer tools are constantly evolving. We experiment with new ideas, ### Execution context selector -This feature displays a button on the console's command line that lets you change the context in which the expression you enter will be executed. (See {{bug(1605154)}} and {{bug(1605153)}} for more details.) +This feature displays a button on the console's command line that lets you change the context in which the expression you enter will be executed. (See [Firefox bug 1605154](https://bugzil.la/1605154) and [Firefox bug 1605153](https://bugzil.la/1605153) for more details.)
@@ -2096,7 +2096,7 @@ This feature displays a button on the console's command line that lets you chang ### Mobile gesture support in Responsive Design Mode -Mouse gestures are used to simulate mobile gestures like swiping/scrolling, double-tap and pinch-zooming and long-press to select/open the context menu. (See {{bug(1621781)}}, {{bug(1245183)}}, and {{bug(1401304)}} for more details.) +Mouse gestures are used to simulate mobile gestures like swiping/scrolling, double-tap and pinch-zooming and long-press to select/open the context menu. (See [Firefox bug 1621781](https://bugzil.la/1621781), [Firefox bug 1245183](https://bugzil.la/1245183), and [Firefox bug 1401304](https://bugzil.la/1401304) for more details.)
@@ -2138,7 +2138,7 @@ Mouse gestures are used to simulate mobile gestures like swiping/scrolling, doub ### Server-sent events in Network Monitor -The Network Monitor displays information for [server-sent](/en-US/docs/Web/API/Server-sent_events) events. (See {{bug(1405706)}} for more details.) +The Network Monitor displays information for [server-sent](/en-US/docs/Web/API/Server-sent_events) events. (See [Firefox bug 1405706](https://bugzil.la/1405706) for more details.)
@@ -2226,7 +2226,7 @@ The CSS Rules View can display browser compatibility tooltips next to any CSS pr ### Desktop zooming -This feature lets you enable smooth pinch zooming on desktop computers without requiring layout reflows, just like mobile devices do. (See {{bug(1245183)}} and {{bug(1620055)}} for more details.) +This feature lets you enable smooth pinch zooming on desktop computers without requiring layout reflows, just like mobile devices do. (See [Firefox bug 1245183](https://bugzil.la/1245183) and [Firefox bug 1620055](https://bugzil.la/1620055) for more details.)
diff --git a/files/en-us/mozilla/firefox/releases/1.5/using_firefox_1.5_caching/index.md b/files/en-us/mozilla/firefox/releases/1.5/using_firefox_1.5_caching/index.md index ba7bb863bd9939a..6bfabdecb070f94 100644 --- a/files/en-us/mozilla/firefox/releases/1.5/using_firefox_1.5_caching/index.md +++ b/files/en-us/mozilla/firefox/releases/1.5/using_firefox_1.5_caching/index.md @@ -33,7 +33,7 @@ Two new browser events enable Web authors to do both. If you use these new events, your pages will continue to display properly in other browsers (we've tested earlier versions of Firefox, Internet Explorer, Opera, and Safari), and will use this new caching functionality when loaded in Firefox 1.5. -Note: as of 10-2009 development versions of Safari added support for these new events (see [the WebKit bug](https://bugs.webkit.org/show_bug.cgi?id=28758)). +Note: as of 10-2009 development versions of Safari added support for these new events (see [the WebKit bug](https://webkit.org/b/28758)). Standard behavior for Web pages is: diff --git a/files/en-us/mozilla/firefox/releases/1.5/what_s_new_in_1.5_alpha/index.md b/files/en-us/mozilla/firefox/releases/1.5/what_s_new_in_1.5_alpha/index.md index d8b7b4301921e61..2b520074ec7ba1a 100644 --- a/files/en-us/mozilla/firefox/releases/1.5/what_s_new_in_1.5_alpha/index.md +++ b/files/en-us/mozilla/firefox/releases/1.5/what_s_new_in_1.5_alpha/index.md @@ -75,11 +75,11 @@ This page is based largely on [https://www.squarefree.com/burningedg...eases/](h - Hidden referrer column for history - - : Extensions can now access the referer information for pages stored in the browser history. This feature can be used to provide alternate history views and other useful functionality. {{bug(128398) }} + - : Extensions can now access the referer information for pages stored in the browser history. This feature can be used to provide alternate history views and other useful functionality. [Firefox bug 128398](https://bugzil.la/128398) - API for prioritizing HTTP connections - - : The Mozilla networking library now supports the prioritization of connections to a specific server using `nsISupportsPriority`. {{bug(278531) }} + - : The Mozilla networking library now supports the prioritization of connections to a specific server using `nsISupportsPriority`. [Firefox bug 278531](https://bugzil.la/278531) - API for managing user and UA stylesheets @@ -87,15 +87,15 @@ This page is based largely on [https://www.squarefree.com/burningedg...eases/](h - API for configuring proxies - - : It is now possible for extensions to easily override the proxy configuration without affecting user-visible preferences. See `nsIProtocolProxyService`, `nsIProtocolProxyFilter`, and `nsIProtocolProxyCallback`. {{bug(282442) }} + - : It is now possible for extensions to easily override the proxy configuration without affecting user-visible preferences. See `nsIProtocolProxyService`, `nsIProtocolProxyFilter`, and `nsIProtocolProxyCallback`. [Firefox bug 282442](https://bugzil.la/282442) - Dynamic Overlays - - : Loading of XUL overlays after the document has been displayed is now supported. See `nsIDOMXULDocument`. {{bug(282103) }} + - : Loading of XUL overlays after the document has been displayed is now supported. See `nsIDOMXULDocument`. [Firefox bug 282103](https://bugzil.la/282103) - E4X - - : The Mozilla JavaScript engine now supports ECMAScript for XML (E4X), a draft ECMA standard that adds native XML datatypes to the language and provides operators for common XML operations. See [the ECMA specification](https://www.ecma-international.org/publications/standards/Ecma-357.htm). {{bug(246441)}} + - : The Mozilla JavaScript engine now supports ECMAScript for XML (E4X), a draft ECMA standard that adds native XML datatypes to the language and provides operators for common XML operations. See [the ECMA specification](https://www.ecma-international.org/publications/standards/Ecma-357.htm). [Firefox bug 246441](https://bugzil.la/246441) - Translucent Windows (Windows/Linux) @@ -104,7 +104,7 @@ This page is based largely on [https://www.squarefree.com/burningedg...eases/](h - Adding tokens to the User-Agent string - : It is now possible for applications, extensions, and vendors to all add tokens to the User-Agent string (using default preferences) without overwriting each other. - See [documentation](/en-US/docs/Web/HTTP/Headers/User-Agent). {{bug(274928)}} + See [documentation](/en-US/docs/Web/HTTP/Headers/User-Agent). [Firefox bug 274928](https://bugzil.la/274928) - Toolkit chrome registry diff --git a/files/en-us/mozilla/firefox/releases/10/index.md b/files/en-us/mozilla/firefox/releases/10/index.md index db2fcec063cab81..5d3cc858e5a68b0 100644 --- a/files/en-us/mozilla/firefox/releases/10/index.md +++ b/files/en-us/mozilla/firefox/releases/10/index.md @@ -19,7 +19,7 @@ Firefox 10 shipped on January 31, 2012. This article provides information about ### JavaScript - The method `WeakMap.set()` now returns `undefined`, instead of itself. -- A bug was introduced in regular expression handling in Firefox 7; this has been fixed. See {{ bug(683838) }} if you want the gory details. +- A bug was introduced in regular expression handling in Firefox 7; this has been fixed. See [Firefox bug 683838](https://bugzil.la/683838) if you want the gory details. - You can no longer use [E4X](/en-US/docs/E4X) syntax while in [ECMAScript 5 strict mode](/en-US/docs/Web/JavaScript/Reference/Strict_mode) (that is, after `"use strict;"`). ### DOM @@ -143,7 +143,7 @@ For an overview of likely issues that may arise when updating your add-ons to su ### Build system changes -- The `--disable-rdf` build option, which actually made it impossible to successfully build, has been removed. Work is ongoing on being able to actually remove RDF support entirely, but at present XUL still requires it to function. See {{ bug(559505) }} for progress on removing the last vestiges of RDF being required. +- The `--disable-rdf` build option, which actually made it impossible to successfully build, has been removed. Work is ongoing on being able to actually remove RDF support entirely, but at present XUL still requires it to function. See [Firefox bug 559505](https://bugzil.la/559505) for progress on removing the last vestiges of RDF being required. - The `--disable-smil` build option has been removed. ### See also diff --git a/files/en-us/mozilla/firefox/releases/100/index.md b/files/en-us/mozilla/firefox/releases/100/index.md index 8da26a6e6c171eb..6f95a778521adbb 100644 --- a/files/en-us/mozilla/firefox/releases/100/index.md +++ b/files/en-us/mozilla/firefox/releases/100/index.md @@ -15,7 +15,7 @@ No notable changes. ### CSS -- CSS media features for [`dynamic-range`](/en-US/docs/Web/CSS/@media/dynamic-range) and [`video-dynamic-range`](/en-US/docs/Web/CSS/@media/video-dynamic-range) are now supported. You can now test whether a user agent or an output device supports the combination of brightness, contrast ratio, and color depth by using `dynamic-range` and in the video plane by using `video-dynamic-range` ({{bug(1751217)}}). +- CSS media features for [`dynamic-range`](/en-US/docs/Web/CSS/@media/dynamic-range) and [`video-dynamic-range`](/en-US/docs/Web/CSS/@media/video-dynamic-range) are now supported. You can now test whether a user agent or an output device supports the combination of brightness, contrast ratio, and color depth by using `dynamic-range` and in the video plane by using `video-dynamic-range` ([Firefox bug 1751217](https://bugzil.la/1751217)). ### JavaScript @@ -25,31 +25,31 @@ No notable changes. #### Removals -- The non-standard {{httpheader("Large-Allocation")}} HTTP header has been removed ({{bug(1598759)}}). +- The non-standard {{httpheader("Large-Allocation")}} HTTP header has been removed ([Firefox bug 1598759](https://bugzil.la/1598759)). ### APIs -- [`WritableStream`](/en-US/docs/Web/API/WritableStream), [`WritableStreamDefaultWriter`](/en-US/docs/Web/API/WritableStreamDefaultWriter), [`WritableStreamDefaultController`](/en-US/docs/Web/API/WritableStreamDefaultController), and [`ReadableStream.pipeTo()`](/en-US/docs/Web/API/ReadableStream/pipeTo) are now supported ({{bug(1759597)}}). +- [`WritableStream`](/en-US/docs/Web/API/WritableStream), [`WritableStreamDefaultWriter`](/en-US/docs/Web/API/WritableStreamDefaultWriter), [`WritableStreamDefaultController`](/en-US/docs/Web/API/WritableStreamDefaultController), and [`ReadableStream.pipeTo()`](/en-US/docs/Web/API/ReadableStream/pipeTo) are now supported ([Firefox bug 1759597](https://bugzil.la/1759597)). #### DOM - Code can now use the static method [`AbortSignal.timeout()`](/en-US/docs/Web/API/AbortSignal/timeout). - This returns an {{domxref("AbortSignal")}} that can be used to automatically abort an operation with `TimeoutError` after a specified time ({{bug(1753309)}}). + This returns an {{domxref("AbortSignal")}} that can be used to automatically abort an operation with `TimeoutError` after a specified time ([Firefox bug 1753309](https://bugzil.la/1753309)). ### WebAssembly - WebAssembly now supports exceptions that can be thrown and caught in either WebAssembly or JavaScript (or some other runtime), crossing between the environment boundaries if not handled. - The JavaScript representations of WebAssembly exceptions are [WebAssembly.Exception](/en-US/docs/WebAssembly/JavaScript_interface/Exception) and [WebAssembly.Tag](/en-US/docs/WebAssembly/JavaScript_interface/Tag) ({{bug(1759217)}}). + The JavaScript representations of WebAssembly exceptions are [WebAssembly.Exception](/en-US/docs/WebAssembly/JavaScript_interface/Exception) and [WebAssembly.Tag](/en-US/docs/WebAssembly/JavaScript_interface/Tag) ([Firefox bug 1759217](https://bugzil.la/1759217)). ### WebDriver conformance (Marionette) -- Added support for user prompts (e.g. `alert`) on Android ({{bug(1708105)}}). +- Added support for user prompts (e.g. `alert`) on Android ([Firefox bug 1708105](https://bugzil.la/1708105)). ## Changes for add-on developers -- The `color_scheme` and `content_color_scheme` properties are added to [theme](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/theme) manifest key and available in the {{WebExtAPIRef("theme")}} API. These properties enable a theme to override whether a light or dark color scheme is automatically applied to the chrome or content ({{bug(1708105)}}). -- You can now create a muted tab using {{WebExtAPIRef("tabs.create()")}} with the new `muted` property in the `createProperties` object ({{bug(1372100)}}). -- Support added for {{WebExtAPIRef("runtime.onSuspend")}} and {{WebExtAPIRef("runtime.onSuspendCanceled")}} improving support for event page features ({{bug(1753850)}}). +- The `color_scheme` and `content_color_scheme` properties are added to [theme](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/theme) manifest key and available in the {{WebExtAPIRef("theme")}} API. These properties enable a theme to override whether a light or dark color scheme is automatically applied to the chrome or content ([Firefox bug 1708105](https://bugzil.la/1708105)). +- You can now create a muted tab using {{WebExtAPIRef("tabs.create()")}} with the new `muted` property in the `createProperties` object ([Firefox bug 1372100](https://bugzil.la/1372100)). +- Support added for {{WebExtAPIRef("runtime.onSuspend")}} and {{WebExtAPIRef("runtime.onSuspendCanceled")}} improving support for event page features ([Firefox bug 1753850](https://bugzil.la/1753850)). ## Older versions diff --git a/files/en-us/mozilla/firefox/releases/101/index.md b/files/en-us/mozilla/firefox/releases/101/index.md index b4f89755edf7b09..441ea863538f937 100644 --- a/files/en-us/mozilla/firefox/releases/101/index.md +++ b/files/en-us/mozilla/firefox/releases/101/index.md @@ -15,11 +15,11 @@ No notable changes. ### CSS -- The [`prefers-contrast`](/en-US/docs/Web/CSS/@media/prefers-contrast) media feature that is used to detect whether the user has specified a preference for higher (`more`) or lower (`less`) contrast in the presentation of web content is now available by default. This feature now also lets users specify a set of colors to use for the contrast through the new `custom` value ({{bug(1656363)}}). +- The [`prefers-contrast`](/en-US/docs/Web/CSS/@media/prefers-contrast) media feature that is used to detect whether the user has specified a preference for higher (`more`) or lower (`less`) contrast in the presentation of web content is now available by default. This feature now also lets users specify a set of colors to use for the contrast through the new `custom` value ([Firefox bug 1656363](https://bugzil.la/1656363)). -- Three new viewport sizes have been introduced: small (`s`), large (`l`), and dynamic (`d`). These new sizes have added new [viewport-percentage length units](/en-US/docs/Web/CSS/length) in addition to the existing ones - `vh`, `vw`, `vmax`, and `vmin`. The new viewport-percentage length units include `svh`, `lvh`, `dvh`, `svw`, `lvw`, `dvw`, `svmax`, `lvmax`, `dvmax`, `svmin`, `lvmin`, and `dvmin` ({{bug(1610815)}}). Additionally, the units `vb` and `vi` are now supported by default ({{bug(1610815)}}). +- Three new viewport sizes have been introduced: small (`s`), large (`l`), and dynamic (`d`). These new sizes have added new [viewport-percentage length units](/en-US/docs/Web/CSS/length) in addition to the existing ones - `vh`, `vw`, `vmax`, and `vmin`. The new viewport-percentage length units include `svh`, `lvh`, `dvh`, `svw`, `lvw`, `dvw`, `svmax`, `lvmax`, `dvmax`, `svmin`, `lvmin`, and `dvmin` ([Firefox bug 1610815](https://bugzil.la/1610815)). Additionally, the units `vb` and `vi` are now supported by default ([Firefox bug 1610815](https://bugzil.la/1610815)). -- Support for the [`inline-size`](/en-US/docs/Web/CSS/contain#inline-size) value for the `contain` property has been added. For more information, see ({{bug(1755565)}}). +- Support for the [`inline-size`](/en-US/docs/Web/CSS/contain#inline-size) value for the `contain` property has been added. For more information, see ([Firefox bug 1755565](https://bugzil.la/1755565)). ### JavaScript @@ -30,31 +30,31 @@ No notable changes. #### DOM - [`HTMLMediaElement.preservesPitch`](/en-US/docs/Web/API/HTMLMediaElement/preservesPitch) is now supported without the `moz` prefix. - `mozPreservesPitch` is now an alias of `preservesPitch`, but is deprecated, and may be removed in future releases ({{bug(1652950)}}). + `mozPreservesPitch` is now an alias of `preservesPitch`, but is deprecated, and may be removed in future releases ([Firefox bug 1652950](https://bugzil.la/1652950)). -- [`HTMLInputElement.showPicker()`](/en-US/docs/Web/API/HTMLInputElement/showPicker) is now supported, allowing the picker for an input element to be displayed when a user interacts with some other element, such as a button ({{bug(1745005)}}). +- [`HTMLInputElement.showPicker()`](/en-US/docs/Web/API/HTMLInputElement/showPicker) is now supported, allowing the picker for an input element to be displayed when a user interacts with some other element, such as a button ([Firefox bug 1745005](https://bugzil.la/1745005)). -- [`DOMException`](/en-US/docs/Web/API/DOMException) is now a {{Glossary("serializable object")}}, so it can be cloned with {{domxref("structuredClone()")}} or copied between [workers](/en-US/docs/Web/API/Worker) using {{domxref("Worker.postMessage()", "postMessage()")}} ({{bug(1561357)}}). +- [`DOMException`](/en-US/docs/Web/API/DOMException) is now a {{Glossary("serializable object")}}, so it can be cloned with {{domxref("structuredClone()")}} or copied between [workers](/en-US/docs/Web/API/Worker) using {{domxref("Worker.postMessage()", "postMessage()")}} ([Firefox bug 1561357](https://bugzil.la/1561357)). - _Constructable stylesheets_ are now supported, making it much easier to create reusable stylesheets for use with [Shadow DOM](/en-US/docs/Web/Web_Components/Using_shadow_DOM). The update includes the addition of a [`CSSStyleSheet()` constructor](/en-US/docs/Web/API/CSSStyleSheet/CSSStyleSheet) for creating new stylesheets, the {{domxref("CSSStyleSheet.replace()")}} and {{domxref("CSSStyleSheet.replaceSync()")}} methods that can be used to add/replace CSS rules in the sheet, and the [`Document.adoptedStyleSheets`](/en-US/docs/Web/API/Document/adoptedStyleSheets) and [`ShadowRoot.adoptedStyleSheets`](/en-US/docs/Web/API/ShadowRoot/adoptedStyleSheets) properties that are used to share sheets to a document and its shadow DOM subtrees. - See {{bug(1520690)}} for more information. + See [Firefox bug 1520690](https://bugzil.la/1520690) for more information. #### Media, WebRTC, and Web Audio - [AV1 codec parameters](/en-US/docs/Web/Media/Formats/codecs_parameter#av1) are now properly parsed in media support queries. This means that [`MediaCapabilities.decodingInfo()`](/en-US/docs/Web/API/MediaCapabilities/decodingInfo), [`HTMLMediaElement.canPlayType()`](/en-US/docs/Web/API/HTMLMediaElement/canPlayType), and [`MediaSource.isTypeSupported()`](/en-US/docs/Web/API/MediaSource/isTypeSupported) will now accurately report support for playback for AV1 sources based on the provided codec parameters. [`MediaCapabilities.decodingInfo()`](/en-US/docs/Web/API/MediaCapabilities/decodingInfo) will also use the information to accurately report on "efficient decoding" of AV1 videos. - For more information, see {{bug(1757861)}}. + For more information, see [Firefox bug 1757861](https://bugzil.la/1757861). - [`RTCRtpEncodingParameters.maxFramerate`](/en-US/docs/Web/API/RTCRtpEncodingParameters/maxFramerate) is now supported for setting the maximum framerate that can be used to send an encoding (in {{domxref("RTCPeerConnection.addTransceiver()")}} and {{domxref("RTCRtpSender.setParameters()")}}). Note that zero if a valid frame rate value, but is interpreted by Firefox as "no frame rate limit". - For more information, see {{bug(1611957)}}. + For more information, see [Firefox bug 1611957](https://bugzil.la/1611957). #### SVG - SVG images in the Firefox UI that are styled using [`prefers-color-scheme`](/en-US/docs/Web/CSS/@media/prefers-color-scheme) will respect the [`color-scheme`](/en-US/docs/Web/CSS/color-scheme) of the embedder (previously `prefers-color-scheme` ignored the `color-scheme` of the embedder and triggered off either the device or browser theme). - This ensures that a favicon, for example, is always styled to match the theme of the elements that nest it, and not necessarily the (potentially different) theme of the device. ({{bug(1764354)}}). + This ensures that a favicon, for example, is always styled to match the theme of the elements that nest it, and not necessarily the (potentially different) theme of the device. ([Firefox bug 1764354](https://bugzil.la/1764354)). ### WebDriver conformance (WebDriver BiDi, Marionette) @@ -72,14 +72,14 @@ For more information, see the [full bug list](https://bugzilla.mozilla.org/bugli ## Changes for add-on developers -- Addition of the {{WebExtAPIRef("scripting")}} API, which provides features to execute a script, insert and remove CSS, and manage the registration of content scripts ({{bug(1687764)}}). This API is available to Manifest V3 extensions and takes over the execute script and insert and remove CSS features from the {{WebExtAPIRef("tabs")}} API. +- Addition of the {{WebExtAPIRef("scripting")}} API, which provides features to execute a script, insert and remove CSS, and manage the registration of content scripts ([Firefox bug 1687764](https://bugzil.la/1687764)). This API is available to Manifest V3 extensions and takes over the execute script and insert and remove CSS features from the {{WebExtAPIRef("tabs")}} API. - Addition of the {{WebExtAPIRef("action")}} API, which takes over the features of the {{WebExtAPIRef("browserAction")}} API in Manifest V3 extensions. Corresponding addition of the [`"action"`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/action) manifest key and [`_execute_action` special shortcut](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/commands#special_shortcuts) to the manifest `commands` key. Note that the {{WebExtAPIRef("browserAction")}} API and [`"browser_action"`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_action) manifest key are only available in Manifest V2 extensions. - The [`"background"`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/background) manifest key property `"persistent"` can be set to `false` under the control of preferences: for Manifest V2, the extensions.eventPages.enabled preference, and in Manifest V3, the extensions.manifestV3.enabled preference. - Addition of the [`"host_permissions"`](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/host_permissions) manifest key, which is available for Manifest V3 extensions. - The content script execution environment has changed for Manifest V3 extensions: - Content scripts can no longer rely on host permissions to perform cross-origin requests. Cross-origin requests from content scripts are possible with [CORS](/en-US/docs/Web/HTTP/CORS). - The `content` object (that offered `content.fetch`, `content.XMLHttpRequest`, and `content.WebSocket`) is removed from the content script execution environment. -- Addition of the {{WebExtAPIRef("storage.StorageArea.onChanged")}} event that enables you to listen for changes in content in the `local` and `sync` storage areas ({{bug(1758475)}}). +- Addition of the {{WebExtAPIRef("storage.StorageArea.onChanged")}} event that enables you to listen for changes in content in the `local` and `sync` storage areas ([Firefox bug 1758475](https://bugzil.la/1758475)). ### Removals diff --git a/files/en-us/mozilla/firefox/releases/102/index.md b/files/en-us/mozilla/firefox/releases/102/index.md index b828c8d9f79402b..1538e6d7b891d44 100644 --- a/files/en-us/mozilla/firefox/releases/102/index.md +++ b/files/en-us/mozilla/firefox/releases/102/index.md @@ -15,7 +15,7 @@ No notable changes. ### CSS -The [`update`](/en-US/docs/Web/CSS/@media/update-frequency) media feature that can be used to query the ability of the output device to modify the appearance of content after it is rendered is now available by default ({{bug(1422312)}}). +The [`update`](/en-US/docs/Web/CSS/@media/update-frequency) media feature that can be used to query the ability of the output device to modify the appearance of content after it is rendered is now available by default ([Firefox bug 1422312](https://bugzil.la/1422312)). ### JavaScript @@ -23,43 +23,43 @@ No notable changes. ### APIs -- The Non-standard interfaces [IDBMutableFile](/en-US/docs/Web/API/IDBMutableFile), [IDBFileHandle](/en-US/docs/Web/API/IDBFileHandle), [IDBFileRequest](/en-US/docs/Web/API/IDBFileRequest), and the method [IDBDatabase.createMutableFile()](/en-US/docs/Web/API/IDBDatabase#idbdatabase.createmutablefile) have been disabled by default in preparation for removal in a future release ({{bug(1764771)}}). +- The Non-standard interfaces [IDBMutableFile](/en-US/docs/Web/API/IDBMutableFile), [IDBFileHandle](/en-US/docs/Web/API/IDBFileHandle), [IDBFileRequest](/en-US/docs/Web/API/IDBFileRequest), and the method [IDBDatabase.createMutableFile()](/en-US/docs/Web/API/IDBDatabase#idbdatabase.createmutablefile) have been disabled by default in preparation for removal in a future release ([Firefox bug 1764771](https://bugzil.la/1764771)). - [Transform streams](/en-US/docs/Web/API/TransformStream) are now supported, allowing you to pipe from {{domxref("ReadableStream")}} to a {{domxref("WritableStream")}}, executing a transformation on the chunks. - The update includes the new interfaces [`TransformStream`](/en-US/docs/Web/API/TransformStream) and [`TransformStreamDefaultController`](/en-US/docs/Web/API/TransformStreamDefaultController) and the method [`ReadableStream.pipeThrough()`](/en-US/docs/Web/API/ReadableStream/pipeThrough) ({{bug(1767507)}}). + The update includes the new interfaces [`TransformStream`](/en-US/docs/Web/API/TransformStream) and [`TransformStreamDefaultController`](/en-US/docs/Web/API/TransformStreamDefaultController) and the method [`ReadableStream.pipeThrough()`](/en-US/docs/Web/API/ReadableStream/pipeThrough) ([Firefox bug 1767507](https://bugzil.la/1767507)). - [Readable byte streams](/en-US/docs/Web/API/Streams_API/Using_readable_byte_streams) are now supported, allowing efficient zero-byte transfer of data from an underlying byte source to a consumer (bypassing the stream's internal queues). - The new interfaces are {{domxref("ReadableStreamBYOBReader")}}, {{domxref("ReadableByteStreamController")}} and {{domxref("ReadableStreamBYOBRequest")}} ({{bug(1767342)}}). + The new interfaces are {{domxref("ReadableStreamBYOBReader")}}, {{domxref("ReadableByteStreamController")}} and {{domxref("ReadableStreamBYOBRequest")}} ([Firefox bug 1767342](https://bugzil.la/1767342)). ### Security - Support of the [`wasm-unsafe-eval`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_webassembly_execution) CSP policy directive has been implemented. - A document with a CSP that restricts scripts will no longer load and execute WebAssembly unless the CSP uses `'wasm-unsafe-eval'` or the existing `'unsafe-eval'` keyword ({{bug(1740263)}}). + A document with a CSP that restricts scripts will no longer load and execute WebAssembly unless the CSP uses `'wasm-unsafe-eval'` or the existing `'unsafe-eval'` keyword ([Firefox bug 1740263](https://bugzil.la/1740263)). #### DOM -- The Firefox-only property {{domxref("Window.sidebar")}} has been moved behind a preference and is planned for removal ({{bug(1768486)}}). +- The Firefox-only property {{domxref("Window.sidebar")}} has been moved behind a preference and is planned for removal ([Firefox bug 1768486](https://bugzil.la/1768486)). ### WebDriver conformance #### WebDriver BiDi - There are some improvements to Webdriver BiDi's `browsingContext.navigate` - - Fixed edge cases where the navigation could incorrectly timeout ({{bug(1766217)}}). - - Added support for hash changes ({{bug(1763127)}}). - - Added support navigation to error pages ({{bug(1763124)}}). + - Fixed edge cases where the navigation could incorrectly timeout ([Firefox bug 1766217](https://bugzil.la/1766217)). + - Added support for hash changes ([Firefox bug 1763127](https://bugzil.la/1763127)). + - Added support navigation to error pages ([Firefox bug 1763124](https://bugzil.la/1763124)). #### Marionette -- Allow marionette to connect to a windowless instance of Firefox ({{bug(1726465)}}). -- Fixed issue where `WebDriver:Navigate` with a PageLoadStrategy of "none" returns before navigation has started ({{bug(1754132)}}). -- Fixed a potential race condition in `WebDriver:SwitchToWindow` when switching to a different tab ({{bug(1749666)}}). +- Allow marionette to connect to a windowless instance of Firefox ([Firefox bug 1726465](https://bugzil.la/1726465)). +- Fixed issue where `WebDriver:Navigate` with a PageLoadStrategy of "none" returns before navigation has started ([Firefox bug 1754132](https://bugzil.la/1754132)). +- Fixed a potential race condition in `WebDriver:SwitchToWindow` when switching to a different tab ([Firefox bug 1749666](https://bugzil.la/1749666)). ## Changes for add-on developers -- The {{WebExtAPIRef("scripting")}} API, which provides features to execute script, insert and remove CSS, and manage the registration of content scripts is now available to Manifest V2 extensions ({{bug(1766615)}}). -- With the introduction of support for the 'wasm-unsafe-eval' CSP keyword in Firefox ({{bug(1740263)}}), Manifest V3 extensions are now required to specify this keyword in the [content_security_policy](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy) manifest key to use [WebAssembly](/en-US/docs/WebAssembly). For backwards-compatibility, Manifest V2 extensions can still use WebAssembly without the keyword ({{bug(1766027)}}). -- The `nonPersistentCookies` option of the {{WebExtAPIRef("privacy.websites")}} `cookieConfig` property has been deprecated ({{bug(1754924)}}). +- The {{WebExtAPIRef("scripting")}} API, which provides features to execute script, insert and remove CSS, and manage the registration of content scripts is now available to Manifest V2 extensions ([Firefox bug 1766615](https://bugzil.la/1766615)). +- With the introduction of support for the 'wasm-unsafe-eval' CSP keyword in Firefox ([Firefox bug 1740263](https://bugzil.la/1740263)), Manifest V3 extensions are now required to specify this keyword in the [content_security_policy](/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy) manifest key to use [WebAssembly](/en-US/docs/WebAssembly). For backwards-compatibility, Manifest V2 extensions can still use WebAssembly without the keyword ([Firefox bug 1766027](https://bugzil.la/1766027)). +- The `nonPersistentCookies` option of the {{WebExtAPIRef("privacy.websites")}} `cookieConfig` property has been deprecated ([Firefox bug 1754924](https://bugzil.la/1754924)). ## Older versions diff --git a/files/en-us/mozilla/firefox/releases/103/index.md b/files/en-us/mozilla/firefox/releases/103/index.md index d30cd7ea2cb55de..2bd7098be55a329 100644 --- a/files/en-us/mozilla/firefox/releases/103/index.md +++ b/files/en-us/mozilla/firefox/releases/103/index.md @@ -14,20 +14,20 @@ This article provides information about the changes in Firefox 103 that will aff #### Removals - Support for the `` element has been removed along with the `dom.menuitem.enabled` preference. - For more details, see [Bug 1372276](https://bugzilla.mozilla.org/show_bug.cgi?id=1372276). + For more details, see [Bug 1372276](https://bugzil.la/1372276). ### MathML #### Removals -- The deprecated `scriptminsize` and `scriptsizemultiplier` attributes have been removed ({{bug(1772697)}}). +- The deprecated `scriptminsize` and `scriptsizemultiplier` attributes have been removed ([Firefox bug 1772697](https://bugzil.la/1772697)). ### CSS -- The {{CSSxRef("backdrop-filter")}} property (which can be used to apply graphical effects such as blurring or color shifting to the area behind an element) is now available by default. It was earlier behind a preference setting ({{bug(1578503)}}). -- The {{CSSxRef("scroll-snap-stop")}} property is now available ({{bug(1312165)}}). You can use this property's `always` and `normal` values to specify whether or not to pass the snap points, even when scrolling fast. -- Support has been added for the {{CSSxRef(":modal")}} pseudo class. It selects all elements that are in a state in which they exclude all interaction with other elements until the interaction has been dismissed ({{bug(1768535)}}). -- The [`style`](/en-US/docs/Web/CSS/contain#style) value for the `contain` property is now supported. You can use this value for properties that can have effects on more than just an element and its descendants for effects don't escape the containing element. For more information, see ({{bug(1463600)}}). +- The {{CSSxRef("backdrop-filter")}} property (which can be used to apply graphical effects such as blurring or color shifting to the area behind an element) is now available by default. It was earlier behind a preference setting ([Firefox bug 1578503](https://bugzil.la/1578503)). +- The {{CSSxRef("scroll-snap-stop")}} property is now available ([Firefox bug 1312165](https://bugzil.la/1312165)). You can use this property's `always` and `normal` values to specify whether or not to pass the snap points, even when scrolling fast. +- Support has been added for the {{CSSxRef(":modal")}} pseudo class. It selects all elements that are in a state in which they exclude all interaction with other elements until the interaction has been dismissed ([Firefox bug 1768535](https://bugzil.la/1768535)). +- The [`style`](/en-US/docs/Web/CSS/contain#style) value for the `contain` property is now supported. You can use this value for properties that can have effects on more than just an element and its descendants for effects don't escape the containing element. For more information, see ([Firefox bug 1463600](https://bugzil.la/1463600)). ### JavaScript @@ -35,7 +35,7 @@ This article provides information about the changes in Firefox 103 that will aff This includes {{JSxRef("Error")}}, {{JSxRef("EvalError")}}, {{JSxRef("RangeError")}}, {{JSxRef("ReferenceError")}}, {{JSxRef("SyntaxError")}}, {{JSxRef("TypeError")}}, {{JSxRef("URIError")}} and {{JSxRef("AggregateError")}}. Serialized properties include the [`name`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/name), [`message`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/message), [`cause`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause), [`fileName`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/fileName), [`lineNumber`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/lineNumber) and [`columnNumber`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/columnNumber). For {{JSxRef("AggregateError")}} the `message`, `name`, `cause` and `errors` properties are serialized. - See {{bug(1556604)}} for more details. + See [Firefox bug 1556604](https://bugzil.la/1556604) for more details. ### HTTP @@ -49,11 +49,11 @@ No notable changes. - [`ReadableStream`](/en-US/docs/Web/API/ReadableStream), [`WritableStream`](/en-US/docs/Web/API/WritableStream), [`TransformStream`](/en-US/docs/Web/API/TransformStream) are now [Transferable objects](/en-US/docs/Web/API/Web_Workers_API/Transferable_objects), which means that ownership can be transferred when sharing the objects between a window and workers using `postMessage`, or when using [structuredClone()](/en-US/docs/Web/API/structuredClone) to copy an object. After transferring, the original object cannot be used. - See {{bug(1659025)}} for more details. + See [Firefox bug 1659025](https://bugzil.la/1659025) for more details. - [`caches`](/en-US/docs/Web/API/caches), [`CacheStorage`](/en-US/docs/Web/API/CacheStorage), and [`Cache`](/en-US/docs/Web/API/Cache) now require a [secure context](/en-US/docs/Web/Security/Secure_Contexts); the properties/interfaces are not defined if used in an insecure context. Previously `cache` would return a `CacheStorage` that would throw an exception if used outside of a secure context. - See {{bug(1112134)}} for more details. + See [Firefox bug 1112134](https://bugzil.la/1112134) for more details. ### WebAssembly @@ -63,21 +63,21 @@ No notable changes. #### WebDriver BiDi -- Added a preference to disable experimental BiDi commands and events `remote.experimental.enabled` ({{bug(1777951)}}). -- Added a `script` module with an experimental implementation of the `evaluate` command. Only available if `remote.experimental.enabled` is set to `true` ({{bug(1742979)}}). -- Added serialization support for collections with simple values and complex objects, used for instance for the event data of `log.entryAdded` or the return value of `script.evaluate` ({{bug(1770752)}}). -- Fixed an edge case for `browsingContext.navigate` when navigating to a cached image ({{bug(1763133)}}). +- Added a preference to disable experimental BiDi commands and events `remote.experimental.enabled` ([Firefox bug 1777951](https://bugzil.la/1777951)). +- Added a `script` module with an experimental implementation of the `evaluate` command. Only available if `remote.experimental.enabled` is set to `true` ([Firefox bug 1742979](https://bugzil.la/1742979)). +- Added serialization support for collections with simple values and complex objects, used for instance for the event data of `log.entryAdded` or the return value of `script.evaluate` ([Firefox bug 1770752](https://bugzil.la/1770752)). +- Fixed an edge case for `browsingContext.navigate` when navigating to a cached image ([Firefox bug 1763133](https://bugzil.la/1763133)). #### Marionette -- Updated the `platformVersion` capability to be returned as `moz:platformVersion` ({{bug(1771760)}}). -- Removed support for `ChromeElement`; all elements are now serialized as `WebElement` ({{bug(1775036)}} and {{bug(1775064)}}). +- Updated the `platformVersion` capability to be returned as `moz:platformVersion` ([Firefox bug 1771760](https://bugzil.la/1771760)). +- Removed support for `ChromeElement`; all elements are now serialized as `WebElement` ([Firefox bug 1775036](https://bugzil.la/1775036) and [Firefox bug 1775064](https://bugzil.la/1775064)). ## Changes for add-on developers ### Removals -- Removed the ServiceWorker API in WebExtensions (`'serviceWorker' in navigator` now returns `false` when run inside an extension) ({{bug(1593931)}}). +- Removed the ServiceWorker API in WebExtensions (`'serviceWorker' in navigator` now returns `false` when run inside an extension) ([Firefox bug 1593931](https://bugzil.la/1593931)). ## Older versions diff --git a/files/en-us/mozilla/firefox/releases/104/index.md b/files/en-us/mozilla/firefox/releases/104/index.md index 2f71b50f74118a4..effe71dddb4425f 100644 --- a/files/en-us/mozilla/firefox/releases/104/index.md +++ b/files/en-us/mozilla/firefox/releases/104/index.md @@ -21,11 +21,11 @@ No notable changes. - The methods {{jsxref("Array.prototype.findLast()")}}, {{jsxref("Array.prototype.findLastIndex()")}}, {{jsxref("TypedArray.prototype.findLast()")}}, and {{jsxref("TypedArray.prototype.findLastIndex()")}} are now supported. These are used to find the value and index (respectively) of the last element in an {{jsxref("Array")}} or {{jsxref("TypedArray")}} that matches a supplied test function. - (See {{bug(1775026)}} for more details.) + (See [Firefox bug 1775026](https://bugzil.la/1775026) for more details.) - Serialization of [native Error types](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error#error_types) additionally includes the [`stack`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Stack) property when used with [`window.postMessage()`](/en-US/docs/Web/API/Window/postMessage) and [`structuredClone()`](/en-US/docs/Web/API/structuredClone) (on error types that include `stack`). The `stack` is not yet serialized when errors are sent using other APIs, such as [`Worker.postMessage()`](/en-US/docs/Web/API/Worker/postMessage) - (See {{bug(1774866)}} for more details.) + (See [Firefox bug 1774866](https://bugzil.la/1774866) for more details.) ### HTTP @@ -41,24 +41,24 @@ No notable changes. - [`HTMLElement.focus()`](/en-US/docs/Web/API/HTMLElement/focus) now supports the parameter [`option.focusVisible`](/en-US/docs/Web/API/HTMLElement/focus#focusvisible), which can be used force a browser to display visual indication after the element is focused. Note that browsers may automatically provide visual indication on focused elements if the implementation determines that it will improve accessibility. - (See {{bug(1765083)}} for more details.) + (See [Firefox bug 1765083](https://bugzil.la/1765083) for more details.) #### Canvas -- The `fontKerning` property is now supported on [`CanvasRenderingContext2D`](/en-US/docs/Web/API/CanvasRenderingContext2D/fontKerning) and [`OffscreenCanvasRenderingContext2D`](/en-US/docs/Web/API/OffscreenCanvasRenderingContext2D), enabling developers to specify how kerning is used when text is drawn to a canvas or an offscreen canvas ({{bug(1778908)}}). +- The `fontKerning` property is now supported on [`CanvasRenderingContext2D`](/en-US/docs/Web/API/CanvasRenderingContext2D/fontKerning) and [`OffscreenCanvasRenderingContext2D`](/en-US/docs/Web/API/OffscreenCanvasRenderingContext2D), enabling developers to specify how kerning is used when text is drawn to a canvas or an offscreen canvas ([Firefox bug 1778908](https://bugzil.la/1778908)). #### SVG - The [`SVGStyleElement.disabled`](/en-US/docs/Web/API/SVGStyleElement/disabled) property can now be used to disable or enable an SVG style element, or to check its disabled state. This mirrors the behavior of [`HTMLStyleElement.disabled`](/en-US/docs/Web/API/HTMLStyleElement/disabled). - (See {{bug(1712623)}} for more details.) + (See [Firefox bug 1712623](https://bugzil.la/1712623) for more details.) #### Removals - The `options` argument to the [`IDBFactory.open()`](/en-US/docs/Web/API/IDBFactory/open) method has been removed. This option provided a non-standard, and Firefox-only way to make the indicated database persistent. The option was previously deprecated, and users that need this functionality should already have migrated to {{domxref("StorageManager.persist()")}}. - (See {{bug(1354500)}} for more details.) + (See [Firefox bug 1354500](https://bugzil.la/1354500) for more details.) ### WebAssembly @@ -68,13 +68,13 @@ No notable changes. #### WebDriver BiDi -- Added support for `source` to the `log.entryAdded` event ({{bug(1770792)}}). -- Updated the `url` sent for `browsingContext.contextCreated` events to be `about:blank` for newly opened browsing contexts ({{bug(1775141)}}). +- Added support for `source` to the `log.entryAdded` event ([Firefox bug 1770792](https://bugzil.la/1770792)). +- Updated the `url` sent for `browsingContext.contextCreated` events to be `about:blank` for newly opened browsing contexts ([Firefox bug 1775141](https://bugzil.la/1775141)). #### Marionette -- Improved stability and performance when minimizing or restoring windows on Linux ({{bug(1780212)}}). -- Added support for `touch` actions ({{bug(1543337)}}). +- Improved stability and performance when minimizing or restoring windows on Linux ([Firefox bug 1780212](https://bugzil.la/1780212)). +- Added support for `touch` actions ([Firefox bug 1543337](https://bugzil.la/1543337)). ## Changes for add-on developers diff --git a/files/en-us/mozilla/firefox/releases/105/index.md b/files/en-us/mozilla/firefox/releases/105/index.md index f6fcf32c1cdcf54..42276c04c65b650 100644 --- a/files/en-us/mozilla/firefox/releases/105/index.md +++ b/files/en-us/mozilla/firefox/releases/105/index.md @@ -16,39 +16,39 @@ No notable changes. ### CSS - Embedded content, such as SVG definitions and content in an [`