[pull] main from mdn:main

.github/workflows/pr-labeler.yml

@@ -19,7 +19,7 @@ jobs:
     name: Label by path
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/labeler@f27b608878404679385c85cfa523b85ccb86e213 # v6.1.0
+      - uses: actions/labeler@b8dd2d9be0f68b860e7dae5dae7d772984eacd6d # v6.2.0
         with:
           repo-token: "${{ secrets.GITHUB_TOKEN }}"
           sync-labels: true

files/en-us/mozilla/firefox/experimental_features/index.md

@@ -364,20 +364,6 @@ The [`@container`](/en-US/docs/Web/CSS/Reference/At-rules/@container) CSS at-rul
 - `layout.css.attr.enabled`
   - : Set to `true` to enable.
 
-### Fix for nested scrollable areas
-
-This implementation has been added in order to fix an issue where scrollable content was unreachable. If a scrollbar is set to `display: none;` or `width: 0;` then the scrollbars of nested scrollable areas would be stacked on top of each other meaning that some of the content may well be unreachable. This does however mean that the `@supports selector(::-webkit-scrollbar)` check will return `true` even though the [`::-webkit-scrollbar`](/en-US/docs/Web/CSS/Reference/Selectors/::-webkit-scrollbar) pseudo-element is not truly supported. ([Firefox bug 1977511](https://bugzil.la/1977511)).
-
-| Release channel   | Version added | Enabled by default? |
-| ----------------- | ------------- | ------------------- |
-| Nightly           | 151           | Yes                 |
-| Developer Edition | 151           | No                  |
-| Beta              | 151           | No                  |
-| Release           | 151           | No                  |
-
-- `layout.css.fake-webkit-scrollbar.enabled`
-  - : Set to `true` to enable.
-
 ### `<timeline-range-name>` values
 
 The {{cssxref("animation-range-start")}}, {{cssxref("animation-range-end")}} CSS properties and {{cssxref("animation-range")}} shorthand property now support [`<timeline-range-name>`](/en-US/docs/Web/CSS/Reference/Values/timeline-range-name) values. These [`<timeline-range-name>`](/en-US/docs/Web/CSS/Guides/Scroll-driven_animations/Timeline_range_names#timeline_range_names) values allow you to precisely state which segment that a scroll driven animation will take place within. ([Firefox bug 1804775](https://bugzil.la/1804775)).

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

@@ -34,7 +34,9 @@ Firefox 153 is the current [Beta version of Firefox](https://www.firefox.com/en-
 
 <!-- #### Removals -->
 
-<!-- ### CSS -->
+### CSS
+
+- The {{cssxref("::-webkit-scrollbar")}} pseudo-element selector is now recognized, so the `@supports selector(::-webkit-scrollbar)` check returns `true`. Note that this reports the selector as supported even though scrollbar styling via `::-webkit-scrollbar` is not truly implemented. This was added to fix an issue where scrollbars of nested scrollable areas could stack on top of each other. For example, when a scrollbar is set to `display: none` or `width: 0` leaving some content unreachable. ([Firefox bug 2038877](https://bugzil.la/2038877)).
 
 <!-- #### Removals -->
 

files/en-us/web/api/fedcm_api/rp_sign-in/index.md

@@ -172,7 +172,7 @@ With these `mediation` options, auto-reauthentication will occur under the follo
 - The user is signed into the IdP with that account.
 - Auto-reauthentication didn't happen within the last 10 minutes. This restriction is put into place to stop users being auto-reauthenticated immediately after they sign out — which would make for a pretty confusing user experience.
 - The RP hasn't called {{domxref("CredentialsContainer.preventSilentAccess", "preventSilentAccess()")}} after the previous sign in. This can be used by an RP to explicitly disable auto-reauthentication if desired.
-- The UI mode is [passive]().
+- The UI mode is [passive](<>).
 
 When these conditions are met, an attempt to automatically reauthenticate the user starts as soon as the `get()` is invoked. If auto-reauthentication is successful, the user will log into the RP site again, without being shown a confirmation prompt, using the same IdP account and validated token as they did before.
 

files/en-us/web/css/guides/positioned_layout/stacking_context/index.md

@@ -24,7 +24,7 @@ A stacking context is formed, anywhere in the document, by any element in the fo
 - Element with a {{cssxref("position")}} value `fixed` or `sticky`.
 - Element with a {{cssxref("container-type")}} value `size` or `inline-size` set (See [container queries](/en-US/docs/Web/CSS/Guides/Containment/Container_queries)).
 - Element that is a [flex item](/en-US/docs/Web/CSS/Guides/Flexible_box_layout/Basic_concepts) with a {{cssxref("z-index")}} value other than `auto`.
-- Element that is a [grid item]() with {{cssxref("z-index")}} value other than `auto`.
+- Element that is a [grid item](<>) with {{cssxref("z-index")}} value other than `auto`.
 - Element with an {{cssxref("opacity")}} value less than `1`.
 - Element with a {{cssxref("mix-blend-mode")}} value other than `normal`.
 - Element with any of the following properties with a value other than `none`:

package.json

@@ -75,7 +75,7 @@
     "markdownlint-rule-search-replace": "1.2.0",
     "node-html-parser": "^9.0.0",
     "parse-diff": "^0.12.0",
-    "prettier": "3.9.4",
+    "prettier": "3.9.5",
     "tempy": "^3.2.0",
     "yaml": "^2.9.0",
     "yargs": "^18.0.0"