[pull] main from mdn:main

files/en-us/learn_web_development/extensions/server-side/django/authentication/index.md

@@ -140,7 +140,11 @@ That's it! Now you have a "normal library member" account that you will be able
 
 Django provides almost everything you need to create authentication pages to handle login, log out, and password management "out of the box". This includes a URL mapper, views and forms, but it does not include the templates — we have to create our own!
 
-In this section, we show how to integrate the default system into the _LocalLibrary_ website and create the templates. We'll put them in the main project URLs.
+In this section, we show how to integrate the default system into the _LocalLibrary_ website and create the templates.
+
+> [!NOTE]
+> Django does not include a built-in authentication view for initial user registration ("signup").
+> You can create one yourself if needed, but for this tutorial we assume that only librarians are allowed to register users, and that they would do so using the Django admin interface.
 
 > [!NOTE]
 > You don't have to use any of this code, but it is likely that you'll want to because it makes things a lot easier.

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

@@ -88,7 +88,7 @@ You can find more such features on the [Experimental features](/en-US/docs/Mozil
 
 - **Navigation API** (Nightly): `dom.navigation.webidl.enabled`
 
-  Nightly builds now support the Navigation API, which provides the ability to initiate, intercept, and manage browser navigation actions. It can also examine an application's history entries. This is a successor to previous web platform features such as the {{domxref("History API", "", "", "nocode")}} and {{domxref("window.location")}}, which solves their shortcomings and is specifically aimed at the needs of {{glossary("SPA", "single-page applications (SPAs)")}}.
+  Nightly builds now support the [Navigation API](/en-US/docs/Web/API/Navigation_API), which provides the ability to initiate, intercept, and manage browser navigation actions. It can also examine an application's history entries. This is a successor to previous web platform features such as the {{domxref("History API", "", "", "nocode")}} and {{domxref("window.location")}}, which solves their shortcomings and is specifically aimed at the needs of {{glossary("SPA", "single-page applications (SPAs)")}}.
   ([Firefox bug 1979288](https://bugzil.la/1979288)).
 
 - **Relative control points in CSS `shape()` curve commands**: `layout.css.basic-shape-shape.enabled`

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

@@ -61,10 +61,14 @@ Firefox 147 is the current [Beta version of Firefox](https://www.firefox.com/en-
 
 - The {{domxref("Document.activeViewTransition")}} property is now supported, which returns a {{domxref("ViewTransition")}} instance representing the [view transition](/en-US/docs/Web/API/View_Transition_API) currently active on the document. This provides a consistent way to access an active view transition in any context without having to manually store a reference to it for later use. ([Firefox bug 2001836](https://bugzil.la/2001836)).
 - [WebGPU API](/en-US/docs/Web/API/WebGPU_API) support is now enabled for all macOS versions on devices with Apple Silicon processors (previously only macOS Tahoe support was enabled). ([Firefox bug 1993341](https://bugzil.la/1993341)).
-
 - The [Navigation API](/en-US/docs/Web/API/Navigation_API) is now supported.
   This provides the ability to initiate, intercept, and manage browser navigation actions, and to examine an application's history entries. This is a successor to previous web platform features such as the {{domxref("History API", "", "", "nocode")}} and {{domxref("window.location")}}, which solves their shortcomings and is specifically aimed at the needs of {{glossary("SPA", "single-page applications (SPAs)")}}.
   ([Firefox bug 1997962](https://bugzil.la/1997962)).
+- Brotli compression is now supported for both [`CompressionStream`](/en-US/docs/Web/API/CompressionStream/CompressionStream#brotli) and [`DecompressionStream`](/en-US/docs/Web/API/DecompressionStream/DecompressionStream#brotli).
+  ([Firefox bug 1921583](https://bugzil.la/1921583)).
+- Service workers can now be ECMAScript [module scripts](/en-US/docs/Web/JavaScript/Guide/Modules).
+  To load a service worker module, specify a [`type`](/en-US/docs/Web/API/ServiceWorkerContainer/register#type) of `'module'` when calling {{domxref("ServiceWorkerContainer.register()")}}.
+  ([Firefox bug 1360870](https://bugzil.la/1360870)).
 
 <!-- #### DOM -->
 

files/en-us/web/api/compressionstream/compressionstream/index.md

@@ -20,13 +20,17 @@ new CompressionStream(format)
 
 - `format`
   - : One of the following allowed compression formats:
+    - `"brotli"`
+      - : Compresses the stream using the [Brotli](https://www.rfc-editor.org/rfc/rfc1952) algorithm.
     - `"gzip"`
       - : Compresses the stream using the [GZIP](https://www.rfc-editor.org/rfc/rfc1952) format.
     - `"deflate"`
       - : Compresses the stream using the [DEFLATE](https://www.rfc-editor.org/rfc/rfc1950) algorithm in ZLIB Compressed Data Format.
         The ZLIB format includes a header with information about the compression method and the uncompressed size of the data, and a trailing checksum for verifying the integrity of the data
     - `"deflate-raw"`
       - : Compresses the stream using the [DEFLATE](https://www.rfc-editor.org/rfc/rfc1951) algorithm without a header and trailing checksum.
+    - `"zstd"`
+      - : Compresses the stream using the [ZSTD](https://datatracker.ietf.org/doc/html/rfc8478) algorithm.
 
 ### Exceptions
 

files/en-us/web/api/decompressionstream/decompressionstream/index.md

@@ -20,13 +20,17 @@ new DecompressionStream(format)
 
 - `format`
   - : One of the following compression formats:
+    - `"brotli"`
+      - : Decompress the stream using the [Brotli](https://www.rfc-editor.org/rfc/rfc1952) algorithm.
     - `"gzip"`
-      - : Decompress the stream using the [GZIP](https://www.rfc-editor.org/rfc/rfc1952) format.
+      - : Decompress the stream using the [GZIP](https://www.rfc-editor.org/rfc/rfc1952) algorithm.
     - `"deflate"`
       - : Decompress the stream using the [DEFLATE](https://www.rfc-editor.org/rfc/rfc1950) algorithm in ZLIB Compressed Data Format.
         The ZLIB format includes a header with information about the compression method and the uncompressed size of the data, and a trailing checksum for verifying the integrity of the data
     - `"deflate-raw"`
       - : Decompress the stream using the [DEFLATE](https://www.rfc-editor.org/rfc/rfc1951) algorithm without a header and trailing checksum.
+    - `"zstd"`
+      - : Decompress the stream using the [ZSTD](https://datatracker.ietf.org/doc/html/rfc8478) algorithm.
 
 ### Exceptions
 

files/en-us/web/api/navigation/reload/index.md

@@ -8,8 +8,9 @@ browser-compat: api.Navigation.reload
 
 {{APIRef("Navigation API")}}
 
-The **`reload()`** method of the
-{{domxref("Navigation")}} interface reloads the current URL, updating any provided state in the history entries list.
+The **`reload()`** method of the {{domxref("Navigation")}} interface reloads the current URL, updating any provided state in the history entries list.
+
+Note that `reload()` does not trigger the [`popstate` event](/en-US/docs/Web/API/Window/popstate_event), as this is only fired for soft navigations that cause a "traversal" of the history entries.
 
 ## Syntax
 
@@ -23,9 +24,13 @@ reload(options)
 - `options` {{optional_inline}}
   - : An options object containing the following properties:
     - `state` {{optional_inline}}
-      - : Developer-defined information to be stored in the associated {{domxref("NavigationHistoryEntry")}} once the navigation is complete, retrievable via {{domxref("NavigationHistoryEntry.getState", "getState()")}}. This can be any data type. You might, for example, wish to store a page visit count for analytics purposes, or store UI state details so the view can be shown exactly as the user last left it. Any data stored in `state` must be [structured-cloneable](/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm).
+      - : Developer-defined information to be stored in the associated {{domxref("NavigationHistoryEntry")}} once the navigation is complete, retrievable via {{domxref("NavigationHistoryEntry.getState", "getState()")}}.
+        This can be any data type. You might, for example, wish to store a page visit count for analytics purposes, or store UI state details so the view can be shown exactly as the user last left it.
+        Any data stored in `state` must be [structured-cloneable](/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm).
     - `info` {{optional_inline}}
-      - : Developer-defined information to be passed along to the {{domxref("Navigation/navigate_event", "navigate")}} event, made available in {{domxref("NavigateEvent.info")}}. This can be any data type. You might, for example, wish to display newly-navigated content with a different animation depending on how it was navigated to (swipe left, swipe right, or go home). A string indicating which animation to use could be passed in as `info`.
+      - : Developer-defined information to be passed along to the {{domxref("Navigation/navigate_event", "navigate")}} event, made available in {{domxref("NavigateEvent.info")}}.
+        This can be any data type. You might, for example, wish to display newly-navigated content with a different animation depending on how it was navigated to (swipe left, swipe right, or go home).
+        A string indicating which animation to use may be passed in as `info`.
 
 ### Return value
 

files/jsondata/InterfaceData.json

@@ -2484,6 +2484,10 @@
       "inh": "Sensor",
       "impl": []
     },
+    "Origin": {
+      "inh": "",
+      "impl": []
+    },
     "OscillatorNode": {
       "inh": "AudioScheduledSourceNode",
       "impl": []
@@ -2628,6 +2632,10 @@
       "inh": "",
       "impl": []
     },
+    "PerformanceTimingConfidence": {
+      "inh": "",
+      "impl": []
+    },
     "PeriodicSyncEvent": {
       "inh": "ExtendableEvent",
       "impl": []