Merge branch 'main' into referenceTarget

Author: meyerweb

.github/CODEOWNERS

@@ -35,8 +35,9 @@
 # MathML
 /files/en-us/web/mathml/ @mdn/mathml
 
-# Templates and sidebars (rari)
+# L10n for Macros (rari)
 /files/jsondata/L10n-Template.json @mdn/engineering
+/files/jsondata/L10n-CSSFormalDefinitions.json @mdn/engineering
 
 # ============================= CONTROL FILES ============================= #
 # The CODEOWNERS file must end with these matches: Any pull request changing

.vscode/cspell.json

@@ -28,7 +28,8 @@
   "ignorePaths": [
     ".vscode/cspell.json",
     ".vscode/extensions.json",
-    ".markdownlint-cli2.jsonc"
+    ".markdownlint-cli2.jsonc",
+    "files/jsondata/L10n-*.json"
   ],
   "ignoreRegExpList": [
     // macros

files/en-us/glossary/base64/index.md

@@ -56,7 +56,7 @@ Browsers also natively provide two JavaScript functions for decoding and encodin
 > [!NOTE]
 > Base64 is a binary encoding rather than a text encoding, but `btoa` and `atob` were added to the web platform before it supported binary data types. As a result, the two functions use strings to represent binary data, with the {{glossary("code point")}} of each character representing the value of each byte. This has led to a common misconception that `btoa` can be used to encode arbitrary text data — for example, creating a Base64 `data:` URL of a text or HTML document.
 >
-> However, the byte-to-code-point correspondence only reliably holds true for code points up to `0x7f`. Furthermore, code points over `0xff` will cause `btoa` to throw an error due to exceeding the maximum value for 1 byte. The next section details how to work around this limitation when encoding arbitrary Unicode text.
+> However, the byte-to-code-point correspondence only reliably holds true for code points up to `0x7f`. Furthermore, code points over `0xff` will cause `btoa` to throw an error due to exceeding the maximum value for 1 byte. The {{domxref("Window.btoa()")}} "[Unicode strings](/en-US/docs/Web/API/Window/btoa#unicode_strings)" section details how to work around this limitation when encoding arbitrary Unicode text.
 
 ## See Also
 

files/en-us/learn_web_development/core/scripting/build_your_own_function/index.md

@@ -233,7 +233,7 @@ On to the next parameter. This one is going to involve slightly more work — we
 1. First of all, download the icons needed for this exercise ([warning](https://github.com/mdn/learning-area/blob/main/javascript/building-blocks/functions/icons/warning.png) and [chat](https://github.com/mdn/learning-area/blob/main/javascript/building-blocks/functions/icons/chat.png)) from GitHub. Save them in a new folder called `icons` in the same location as your HTML file.
 
    > [!NOTE]
-   > The warning and chat icons were originally found on [iconfinder.com](https://www.iconfinder.com/), and designed by [Nazarrudin Ansyari](https://www.iconfinder.com/nazarr) — Thanks! (The actual icon pages were since moved or removed.)
+   > The warning and chat icons were originally found on iconfinder.com, and designed by Nazarrudin Ansyari — Thanks! (The actual icon pages were since moved or removed.)
 
 2. Next, find the CSS inside your HTML file. We'll make a few changes to make way for the icons. First, update the `.msgBox` width from:
 

files/en-us/learn_web_development/core/scripting/debugging_javascript/index.md

@@ -61,7 +61,7 @@ There are a number of common JavaScript problems that you will want to be mindfu
 - Making sure [asynchronous operations](/en-US/docs/Learn_web_development/Extensions/Async_JS) have completed before trying to use the values they return. This usually means understanding how to use _promises_: using [`await`](/en-US/docs/Web/JavaScript/Reference/Operators/await) appropriately or running the code to handle the result of an asynchronous call in the promise's {{jsxref("Promise.then()", "then()")}} handler. See [How to use promises](/en-US/docs/Learn_web_development/Extensions/Async_JS/Promises) for an introduction to this topic.
 
 > [!NOTE]
-> [Buggy JavaScript Code: The 10 Most Common Mistakes JavaScript Developers Make](https://www.toptal.com/javascript/10-most-common-javascript-mistakes) has some nice discussions of these common mistakes and more.
+> [Buggy JavaScript Code: The 10 Most Common Mistakes JavaScript Developers Make](https://www.toptal.com/developers/javascript/10-most-common-javascript-mistakes) has some nice discussions of these common mistakes and more.
 
 ## The Browser JavaScript console
 

files/en-us/mdn/writing_guidelines/writing_style_guide/index.md

@@ -695,7 +695,6 @@ If you have questions about usage and style not covered in this guide, we recomm
 If you're interested in improving your writing and editing skills, you may find the following resources to be helpful.
 
 - [Common errors in English usage](https://brians.wsu.edu/common-errors-in-english-usage/) on brians.wsu.edu
-- [English grammar FAQ](https://websites.umich.edu/~jlawler/aue.html) on alt-usage-english.org
 - [English language and usage](https://english.stackexchange.com/) on english.stackexchange.com: Question and answer site for English language usage
 - [Merriam-Webster's Concise Dictionary of English Usage](https://books.google.com/books?id=UDIjAQAAIAAJ) on google.com/books (published 2002): Scholarly but user-friendly, evidence-based advice; very good for non-native speakers, especially for preposition usage
 - [On Writing Well](https://www.harpercollins.com/products/on-writing-well-william-zinsser) by William Zinsser on harpercollins.com (published 2016)

files/en-us/mozilla/add-ons/webextensions/add_a_button_to_the_toolbar/index.md

@@ -54,7 +54,7 @@ Next, create the "icons" directory inside the "buttons" directory, and save the
 !["32 pixel icon of a lined sheet of paper"](page-32.png)
 
 > [!NOTE]
-> These icons are from the [bitsies!](https://www.iconfinder.com/iconsets/bitsies) iconset created by Recep Kütük.
+> These icons are from the "bitsies!" iconset on iconfinder.com created by Recep Kütük.
 
 We have two icons so we can use the bigger one in high-density displays. The browser will take care of selecting the best icon for the current display.
 

files/en-us/mozilla/add-ons/webextensions/api/menus/itemtype/index.md

@@ -6,19 +6,19 @@ browser-compat: webextensions.api.menus.ItemType
 sidebar: addonsidebar
 ---
 
-The type of menu item.
+The type of the menu item.
 
 ## Type
 
 Values of this type are strings. Possible values are:
 
-- normal
+- `normal`
   - : A menu item that just displays a label.
-- checkbox
+- `checkbox`
   - : A menu item that represents a binary state. It displays a checkmark next to the label. Clicking the item toggles the checkmark. The {{WebExtAPIRef("menus.onClicked")}} listener will be passed two extra properties: "checked", indicating whether the item is checked now, and "wasChecked", indicating whether the item was checked before the click event.
-- radio
+- `radio`
   - : A menu item that represents one of a group of choices. Just like a checkbox, this also displays a checkmark next to the label, and its {{WebExtAPIRef("menus.onClicked")}} listener is passed "checked" and "wasChecked". However, if you create more than one radio item, then the items function as a group of radio items: only one item in the group can be checked, and clicking an item makes it the checked item.
-- separator
+- `separator`
   - : A line separating a group of items.
 
 {{WebExtExamples}}

files/en-us/mozilla/add-ons/webextensions/match_patterns/index.md

@@ -54,7 +54,7 @@ The _scheme_ component may take one of two forms:
 
 ### host
 
-The _host_ component may take one of three forms:
+The _host_ component may take one of these forms:
 
 <table class="fullwidth-table standard-table">
   <thead>
@@ -69,17 +69,18 @@ The _host_ component may take one of three forms:
       <td>Any host.</td>
     </tr>
     <tr>
-      <td><code>*.</code> followed by part of the hostname.</td>
-      <td>The given host and any of its subdomains.</td>
+      <td><code>*.</code> followed by part of the hostname, optionally, including a port.</td>
+      <td>The given host (and port) and any of its subdomains.</td>
     </tr>
     <tr>
-      <td>A complete hostname, without wildcards.</td>
-      <td>Only the given host.</td>
+      <td>A complete hostname, without wildcards, optionally, including a port.</td>
+      <td>Only the host (and port).</td>
     </tr>
   </tbody>
 </table>
 
-_host_ must not include a port number.
+> [!NOTE]
+> Firefox doesn't support the inclusion of a port number due to ([Firefox bug 1362809](https://bugzil.la/1362809)) and ([Firefox bug 1468162](https://bugzil.la/1468162)).
 
 _host_ is optional only if the _scheme_ is "file".
 
@@ -93,10 +94,7 @@ After that, it may subsequently contain any combination of the `*` wildcard and
 
 The value for the _path_ matches against the string which is the URL path plus the [URL query string](https://en.wikipedia.org/wiki/Query_string). This includes the `?` between the two, if the query string is present in the URL. For example, if you want to match URLs on any domain where the URL path ends with `foo.bar`, then you need to use an array of Match Patterns like `["*://*/*foo.bar", "*://*/*foo.bar?*"]`. The `?*` is needed, rather than just `bar*`, in order to anchor the ending `*` as applying to the URL query string and not some portion of the URL path.
 
-Neither the [URL fragment identifier](https://en.wikipedia.org/wiki/Fragment_identifier), nor the `#` which precedes it, are considered as part of the _path_.
-
-> [!NOTE]
-> The path pattern string should not include a port number. Adding a port, as in: `http://localhost:1234/*` causes the match pattern to be ignored. However, `http://localhost:1234` will match with `http://localhost/*`.
+Neither the [URL fragment identifier](https://en.wikipedia.org/wiki/Fragment_identifier) nor the `#` that precedes it are considered as part of the _path_ and are ignored during pattern matching. A match pattern containing `#` will fail to match with any URL.
 
 ### \<all_urls>
 
@@ -192,6 +190,22 @@ The special value `<all_urls>` matches all URLs under any of the supported schem
       </td>
     </tr>
     <tr>
+    <tr>
+      <td>
+        <p><code>https://mozilla.org:8080/</code></p>
+        <p>
+          Match all HTTPS URLs that are hosted at "mozilla.org/" on port 8080.
+          Note: Ports are supported in Chrome, not in Firefox.
+        </p>
+      </td>
+      <td>
+        <p><code>https://mozilla.org:8080/</code></p>
+      </td>
+      <td>
+        <p><code>http://a.mozilla.org/</code><br />(unmatched host)</p>
+        <p><code>http://mozilla.org:8081</code><br />(unmatched host)</p>
+      </td>
+    </tr>
       <td>
         <p><code>ftp://mozilla.org/</code></p>
         <p>Match only "ftp://mozilla.org/".</p>
@@ -323,47 +337,56 @@ The special value `<all_urls>` matches all URLs under any of the supported schem
   </tbody>
 </table>
 
-### Invalid match patterns
+### Invalid or unmatched patterns
 
 <table class="fullwidth-table standard-table">
   <thead>
     <tr>
-      <th scope="col">Invalid pattern</th>
+      <th scope="col">Pattern</th>
+      <th scope="col">Issue</th>
       <th scope="col">Reason</th>
     </tr>
   </thead>
   <tbody>
     <tr>
       <td><code>resource://path/</code></td>
+      <td>Invalid</td>
       <td>Unsupported scheme.</td>
     </tr>
     <tr>
       <td><code>https://mozilla.org</code></td>
+      <td>Invalid</td>
       <td>No path.</td>
     </tr>
+    <tr>
+      <td><code>https://www.mozilla.org/#section1</code></td>
+      <td>Unmatched</td>
+      <td>Contains a reference fragment: the URL that the pattern is matched against has any reference fragment removed before matching.</td>
+    </tr>
     <tr>
       <td><code>https://mozilla.*.org/</code></td>
+      <td>Invalid</td>
       <td>"*" in host must be at the start.</td>
     </tr>
     <tr>
       <td><code>https://*zilla.org/</code></td>
+      <td>Invalid</td>
       <td>"*" in host must be the only character or be followed by ".".</td>
     </tr>
     <tr>
       <td><code>http*://mozilla.org/</code></td>
+      <td>Invalid</td>
       <td>"*" in scheme must be the only character.</td>
     </tr>
-    <tr>
-      <td><code>https://mozilla.org:80/</code></td>
-      <td>Host must not include a port number.</td>
-    </tr>
     <tr>
       <td><code>*://*</code></td>
+      <td>Invalid</td>
       <td>Empty path: this should be <code>*://*/*</code>.</td>
     </tr>
     <tr>
       <td><code>file://*</code></td>
-      <td>Empty path: this should be <code>file:///*</code>.</td>
+      <td>Invalid</td>
+      <td>Empty path: this should be <code>file:///*</code>. <code>file://*</code> is accepted when declared in <code>host_permissions</code> in Chrome, which auto-corrects the entry to <code>file:///*</code>.</td>
     </tr>
   </tbody>
 </table>

files/en-us/mozilla/firefox/releases/145/index.md

@@ -1,8 +1,8 @@
 ---
-title: Firefox 145 release notes for developers (Stable)
-short-title: Firefox 145 (Stable)
+title: Firefox 145 release notes for developers
+short-title: Firefox 145
 slug: Mozilla/Firefox/Releases/145
-page-type: firefox-release-notes-active
+page-type: firefox-release-notes
 sidebar: firefox
 ---