[PEPC] Refactor HTMLPermissionElement to HTMLCapabilityElementBase

This CL refactors the Page Embedded Permission Control (PEPC)
implementation in Blink.

1. Renames HTMLPermissionElement logic to HTMLCapabilityElementBase to
   serve as an abstract base class.
2. Decouples HTMLGeolocationElement, HTMLUserMediaElement, and
   HTMLInstallElement from generic type parsing.
3. Updates HTMLPermissionElement to inherit from
   HTMLCapabilityElementBase, preserving the existing behavior for the
   element as a temporary measure before deprecation.

NO_IFTTT=False positive.

Bug: 448593977
Change-Id: Ica85ccc4745e4765a3457e1a62551de5864e00d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7368050
Reviewed-by: Joey Arhar jarhar@chromium.org
Reviewed-by: Dave Tapuska dtapuska@chromium.org
Cr-Commit-Position: refs/heads/main@{#1584921}

Blink>AI: guard LanguageDetector detect after destroy

Ensure detect() checks session destruction before abort handling
so it throws InvalidStateError instead of dereferencing a null
model. Export LanguageDetector for unit tests and add the
language_detection core dep to link tests. Add a unit test that
exercises detect() after destroy().

Bug: 483762287
Change-Id: I223abc975bb90cba2cf3e1bd86ef52224a617e06
Tests: blink_unittests --gtest_filter=LanguageDetectorTest.DetectAfterDestroyThrows
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7570308
Commit-Queue: Reilly Grant reillyg@chromium.org
Commit-Queue: Sophie Chang sophiechang@chromium.org
Reviewed-by: Sophie Chang sophiechang@chromium.org
Reviewed-by: Reilly Grant reillyg@chromium.org
Cr-Commit-Position: refs/heads/main@{#1584876}

[gap-decorations] Overhaul multicol gap decorations

This CL overhauls the multicol gap decorations implementation to match
more closely with how grid does things. This enables us to take
advantage of the painting architecture set up for painting grid gap
decorations, making the code less specialized and simpler.

Moreover, This also makes the code much more efficient in both time and
memory, effectively improving memory complexity from O(mn) to O(m + n).

At the same time, this CL updates some test expectations to reflect
that, at least for now, as per recent CSSWG discussions, column
decorations are allowed to "go through" row gaps with rule-break: none. This might change depending on discussions with the working
group, but can be easily adjusted if we decide to go that route.

Furthermore, as a result of this refactoring, we no longer need
CrossGapsBefore and can no longer use EdgeState, so we remove
related functions and tests.

virtual/fragmented-oof-in-cb/external/wpt/css/css-break/out-of-flow-in-multicolumn-097.html
and
virtual/fragmented-oof-in-cb/external/wpt/css/css-break/out-of-flow-in-multicolumn-098.html
had to be removed from a section in TestExpectations that signaled them
as passing since they are failing with this CL but they are fixed in
the followup, and are re-added to their original section.

Bug: 357648037
Change-Id: If0fd2183509edcbc3d428c17391d54a8297e3e97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7539476
Reviewed-by: Alison Maher almaher@microsoft.com
Commit-Queue: Javier Contreras javiercon@microsoft.com
Cr-Commit-Position: refs/heads/main@{#1584802}

[Masonry] Update row aspect ratio tests

We have 3 failing row grid-lanes tests where an aspect ratio is not
impacting the number of track auto repeats in the row direction. In
CL:6977628, I explored how to fix this, but it was unclear if this was
failing here (and in grid) for an expected reason.

Per a comment in the CSSWG issue [1], it appears that this may be
expected, so update the test expectations for now to match the existing
behavior. However, the issue is still open, so I will plan to update
these tests if we decide that this is actually in fact unexpected.

[1] w3c/csswg-drafts#12964 (comment)

Bug: 343257585
Change-Id: Ia9bef6a98dc2793953f34c9db99255e8cebb675d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7575039
Reviewed-by: Ian Kilpatrick ikilpatrick@chromium.org
Commit-Queue: Alison Maher almaher@microsoft.com
Cr-Commit-Position: refs/heads/main@{#1584799}

Revert "Bug 1990514: Disable bFPP for a few tests " for causing bug 2016747

This reverts commit 9e6453e05c1b30a79a90764d672116f67a67b771.

Revert "Bug 1990514: Print a warning to the console about the FPP behavior when appropriate r=timhuang"

This reverts commit 89a671e8e84dd62327b239bf25729c7e8f9f504d.

Revert "Bug 1990514: Do not lie about the available screen resolution in PDM or WebDriver r=timhuang"

This reverts commit 832c92e7c12aabb887dce0e125e17bb4fb689157.

Revert "Bug 1990514: Promote Screen Available Resolution and Touch Points to Baseline FPP in Nightly r=timhuang"

This reverts commit 087678381d765f336a407eb753dae3c880a6adc4.

Revert "Bug 1990514: Support Nightly ifdefs in RFPTargetDefaults.inc r=timhuang"

This reverts commit 505c2ab10e45b9b5aa157469d472461f0d811e2a.

gecko-commit: 2ebe84e6b107da0f9558febd8f7935a02ba56a09
gecko-reviewers: jgraham, whimboo

Clear pending exception before calling back into JSAPI in streams error case

Differential Revision: https://phabricator.services.mozilla.com/D282017

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2014580
gecko-commit: d9e04805aac542ec6856d57b485f179239b713f2
gecko-reviewers: saschanaz

[animation-trigger] Add WPTs for replay and play behaviors

Bug: 390314945
Change-Id: I979603cd33b830b2057039afe1473e1f6f7a5908
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7567583
Reviewed-by: Kevin Ellis kevers@chromium.org
Commit-Queue: David Awogbemila awogbemila@chromium.org
Cr-Commit-Position: refs/heads/main@{#1584690}

[Connection-Allowlist] Dedicated workers local and network based

1. Updated URLLoaderFactoryParamsHelper::CreateForWorker: Added a
   network_restrictions_id parameter to allow URLLoaderFactories created
   for workers to be subject to network restrictions.

2. Inheritance in DedicatedWorkerHost:

• The DedicatedWorkerHost now accepts and stores a
  creator_network_restrictions_id representing the restrictions of the
  frame or worker that created it.
• creator_network_restrictions_id is passed to
  WorkerScriptFetcher::CreateAndStart to ensure the initial fetch of the
  worker's main script is subject to the restrictions of the creator.
• For nested workers, the parent worker passes its own network_restrictions_id_ as the creator_network_restrictions_id for the
  nested worker.

3. Refined WorkerScriptFetcher:

• CreateAndStart and CreateScriptLoader now handle both a
  worker_network_restrictions_id (to be used by the response throttle to
  restrict the fetches from the worker) and a
  creator_network_restrictions_id (to restrict the fetch of the script).
• Updated DidCreateScriptLoader to correctly initialize
  PolicyContainerPolicies for the worker, ensuring local workers inherit
  from their creator.

4. Registration in the network service:

• Added NetworkRestrictionsWorkerThrottle which handles calling
  RevokeNetworkForNoncesInNetworkContext. By passing the worker's network
  restrictions id to this throttle, the policy found in the script
  response is automatically registered for the worker.

5. Updated Call Sites:

• RenderFrameHostImpl now passes its network restriction id when
  creating a dedicated worker factory.
• SharedWorkerServiceImpl, EmbeddedWorkerInstance, and
  ServiceWorkerDevToolsAgentHost have been updated to pass std::nullopt
  for the restriction IDs with a TODO for future implementation.

6. Enhanced WPT Tests:

• Added tests in dedicated-worker.sub.window.js verifying that:
  -- Main script fetches are blocked if they are cross-origin relative to
  a restricted creator.
  -- Workers created with an empty Connection-Allowlist: () header are
  unable to perform any fetches.

Bug: 447954811

Change-Id: I755252a9841dccf819d098b0485bc66dee231263
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7535781
Commit-Queue: Shivani Sharma shivanisha@chromium.org
Reviewed-by: Arthur Sonzogni arthursonzogni@chromium.org
Reviewed-by: Yoshisato Yanagisawa yyanagisawa@chromium.org
Reviewed-by: Mike West mkwst@chromium.org
Cr-Commit-Position: refs/heads/main@{#1584680}

Make sure elementFromPoint() test hits span

Fails in all browsers on Mac because the chosen point did not hit the
span text. Offset 8px:8px from top/left should.

Bug: 483394574
Change-Id: Iba275a6c0dff03239409c074da614414320dc37e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7572314
Reviewed-by: Steinar H Gunderson sesse@chromium.org
Commit-Queue: Rune Lillesveen futhark@chromium.org
Cr-Commit-Position: refs/heads/main@{#1584629}

Check if percentages are resolvable in CSSParserLocalContext

Let CSSParserLocalContext check whether percentages can be resolved
without used value information or not for the specified property. Since
some color functions, like color-mix(), shape or transform functions has
their own context when resolving percentages, some of the properties may
have both, percentages that depend on a used value and percentages that
don't (for instance, inside some color function), we need to keep track
whether we are currently parsing values inside some css function.
CSSParserLocalContext keep track of that by maintaining a stack of the
current parsed functions.

Note: the border-image-slice test fails since we expect only simplified
percentages and not kCalcLengthFunction for that property. To be fixed
in next CL.

Bug: 413385732
Change-Id: I937675f2d8e138fc3e23cc401e313eed3dc86b3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7544868
Commit-Queue: Munira Tursunova moonira@google.com
Reviewed-by: Rune Lillesveen futhark@chromium.org
Cr-Commit-Position: refs/heads/main@{#1584580}