merge_pr_56561

Fix carry forward to not override flags from conversion.

The bug occurs because any flags about missing components, generated during conversion of the colour (e.g. HSL->OKLCH it can produce a powerless hue) within are overridden by the source colour's flags.
The change is to make it instead by a disjunction of the source color flag and the flag of the color itself.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2001615
gecko-commit: 158f0879a03b46e52615d5c2ebd748681c1e2245
gecko-reviewers: tlouw, emilio, firefox-style-system-reviewers

merge_pr_56560

Fix parsing of custom media features.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2004653
gecko-commit: e062dae9e7024d530e8f2817ecf7c8b00dc1f716
gecko-reviewers: jwatt

merge_pr_56559

webrtc: unmute tracks until a packet arrives after a receptiveness change

This is gated by kMediaStreamTrackEmptyVideoFrameMonitor for more
deterministic behavior and kWebRtcUnmuteTracksWhenPacketArrives2
which is the new killswitch.

Bug: chromium:40821064
Change-Id: Ib0b87c8178d485565a9ead7883d673354617f858
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7216294
Commit-Queue: Philipp Hancke [email protected]
Reviewed-by: Henrik Boström [email protected]
Reviewed-by: Guido Urdaneta [email protected]
Cr-Commit-Position: refs/heads/main@{#1555346}

merge_pr_56558

Make position-area and default-anchor adjustments take priority over CSS grid CB.

As per https://drafts.csswg.org/css-position/#original-cb they should
happen later. In general, multiple of these adjustments should be rarer
and browsers aren't particularly consistent. It's also unclear to me how
it affects the scrollable containing block stuff, I filed bug 2004596 to
sort that out.

Give a reasonable CB (the grid container's padding rect) down from grid
layout now that we might not use the actual grid CB.

Remove a check for fallbacks that isn't needed since part 1 of
bug 1991929.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1924786
gecko-commit: 12c7da0e492f194854dcdbb9f5515ae5ba7f0e0e
gecko-reviewers: layout-anchor-positioning-reviewers, layout-reviewers, dshin

merge_pr_56557

CSS Highlight API: Don't add invalid static ranges to Selection.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2004005
gecko-commit: fd9997141938dcd70dacea83092ec425a1560fc6
gecko-reviewers: smaug

merge_pr_56556

Revert "Bug 2004005 - CSS Highlight API: Don't add invalid static ranges to Selection. " for causing build bustages on Selection.cpp

This reverts commit 15ee536019d871203b3959f6d3a5b3b412faeafc.

gecko-commit: 8b3b945c8696d51492553f658554cf3a3343adc6
gecko-reviewers: smaug

merge_pr_56555

Add some tests for case-insensitivity of language tag matching.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=2003721
gecko-commit: e957834932b9c818e1e5dcc0ce0ef305b13d500a
gecko-reviewers: layout-reviewers, emilio

merge_pr_56548

Verify script enforcement applies even if the source text is modified before require-trusted-types-for 'script' is set.

Current spec [1] essentially caches the "script text" associated to a
script element: it is initially empty and updated by various APIs calls.
The "prepare the script element" algorithm is modified [2], so that
"child text content" would go through the default policy if it does
not match the cached "script text" [3].

Script enforcement could be alternatively be implemented by flags [4].
In that case, it might be tempting not to update the flags when the API
calls modifying a script are performed before Trusted Types are
actually enforced, with the rationale that these API calls are not
considered untrusted at that time. For a cache-based implementations,
this would be equivalent to not caching the "script text" until the
first time it is set in a context when Trusted Types is enforced.

However, WebKit and Chromium follow the spec and really try and run
the default policy on the script text, even if the script text was
modified before TrustedTypes enforcement got enabled. This PR adds
tests to verify this behavior for HTML and SVG scripts.

For completeness, this also verifies that if we remove the
require-trusted-types-for meta tag before the test is executed, then
TrustedTypes enforcement remains enabled per [5].

[1] https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-scripts
[2] https://w3c.github.io/trusted-types/dist/spec/#slot-value-verification
[3] https://w3c.github.io/trusted-types/dist/spec/#prepare-the-script-text
[4] w3c/trusted-types#579
[5] https://www.w3.org/TR/CSP3/#meta-element

merge_pr_56531

[CSS Modules] Only import sheets with matching ConstructorDocument's

This change adds a test and a CHECK to ensure that the stylesheets
imported into adoptedStyleSheets via the tag's
shadowrootadoptedstylesheets attribute are in the same document.

This matches the existing limitation in
TreeScope::OnAdoptedStyleSheetSet. There is a subsequent DCHECK in
AppendAdoptedStyleSheets, but this is closer to the source for
shadowrootadoptedstylesheets.

A test was added that checks this condition via
Document.parseHTMLUnsafe.

Bug: 448174611
Change-Id: I9002f275885113f6dacc965adc52bd185d6fc4af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7212828
Commit-Queue: Kurt Catti-Schmidt [email protected]
Reviewed-by: Mason Freed [email protected]
Cr-Commit-Position: refs/heads/main@{#1555557}

merge_pr_56511

Classify scroll-markers (#56511)