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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1867569
gecko-commit: b26966a8b4176b72a71e58e606e42940a30d70d6
gecko-reviewers: emilio

Bumps [taskcluster](https://github.com/taskcluster/taskcluster) from 59.2.0 to 60.3.2.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](taskcluster/taskcluster@v59.2.0...v60.3.2)

---
updated-dependencies:
- dependency-name: taskcluster
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [pygithub](https://github.com/pygithub/pygithub) from 2.1.1 to 2.2.0.
- [Release notes](https://github.com/pygithub/pygithub/releases)
- [Changelog](https://github.com/PyGithub/PyGithub/blob/main/doc/changes.rst)
- [Commits](PyGithub/PyGithub@v2.1.1...v2.2.0)

---
updated-dependencies:
- dependency-name: pygithub
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

…eb-platform-tests#44262)

specified in: https://www.w3.org/TR/css-align-3/#valdef-align-content-space-around

decision: w3c/csswg-drafts#5088 (comment)

Bug: 1517655
Change-Id: I348273d53025d3a5389e1867e74c59aee291d0a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5250231
Reviewed-by: Ian Kilpatrick <[email protected]>
Commit-Queue: Ian Kilpatrick <[email protected]>
Reviewed-by: Christian Biesinger <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255119}

The spec was merged here, so the tests should no longer be tentative:
whatwg/html#8467

Bug: 1514397
Change-Id: I121e5e734145ff4cb122fb1bc2f7a5bc146dafca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5151685
Reviewed-by: Mason Freed <[email protected]>
Commit-Queue: Joey Arhar <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255129}

…PT less flaky

Bug: 1515599, 1524064
Change-Id: I6ae7dab6bae07a08437e0f7aa5c815f9a7d6a9f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5258720
Reviewed-by: Dominic Farolino <[email protected]>
Commit-Queue: Garrett Tanzer <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255181}

…kie IDL)

The Storage Access API provides access to unpartitioned cookies in
third-party contexts. This CL is part of a series to extend that access
to SharedWorkers.

Before we actually provide access to SharedWorkers, we need a way for
the renderer to limit the scope of SameSite cookies provided to the
worker. Normally, a worker with a first-party storage key could access
all cookies, but if access is via the SAA handle we want to limit that
access to just SameSite: None cookies.

This CL is part of a series to allow that limiting ability. For now, we
expose the option in IDL but do not implement the change needed to limit
cookie access in first-party contexts when the option is set to 'none'.
The next CL will implement this limit.

Note: The ability to request 'all' in a third-party context is not added
here nor will it be added. We verify that an exception is thrown if this
is attempted.

Explainer:
https://privacycg.github.io/saa-non-cookie-storage/shared-workers.html

Part 1: Expose same-site cookie IPC
Part 2: Expose same-site cookie IDL
Part 3: Implement same-site cookie filtering
Part 4: Add SharedWorker support to SAA handle

Bug: 1484966
Change-Id: I8c56c02025950e119e3967afd49ed684446fd6e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5251551
Reviewed-by: Weizhong Xia <[email protected]>
Auto-Submit: Ari Chivukula <[email protected]>
Commit-Queue: Ari Chivukula <[email protected]>
Reviewed-by: Sun Yueru <[email protected]>
Reviewed-by: Nate Chapin <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255183}

Similar to:
https://chromium-review.googlesource.com/c/chromium/src/+/5250231
https://chromium-review.googlesource.com/c/chromium/src/+/5235235

Makes space-around/space-evenly fallback to safe centering alignment.

See: w3c/csswg-drafts#5088 (comment)

Bug: 1517655
Change-Id: I65b9b5e0540a53b61b61cd2c84d98b41f292ad76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5258681
Commit-Queue: Ian Kilpatrick <[email protected]>
Reviewed-by: Kurt Catti-Schmidt <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255220}

Bug: 1476927
Change-Id: Ia7361777d5fb1457a066d3f62cf73181c9b1f1cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5237290
Reviewed-by: Nicolás Peña <[email protected]>
Commit-Queue: Christian Biesinger <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255296}

Fixed: 1510241
Change-Id: I1ce3571c56fcfd6cc6d57458ff644162588d233a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5259102
Reviewed-by: Mark Schillaci <[email protected]>
Commit-Queue: Aaron Leventhal <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255303}

This CL implements DefineXnnNodeForMatmul() method that defines XNNPACK
matmul Node by xnn_define_batch_matrix_multiply().

For unit tests, this CL implements MatmulTest of MLGraphTest that
checks the compute results of matmul operators.

Bug: 1273291
Change-Id: Ife8e1023804d4b9970bfff067fbeedbf12ba313e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5232604
Commit-Queue: Lisha Guo <[email protected]>
Reviewed-by: ningxin hu <[email protected]>
Reviewed-by: Reilly Grant <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255409}

When crrev.com/c/5052124 started rewinding floats, its
associated parallel flow break tokens should also be reset,
but it didn't. This patch fixes it.

The 3 tests are for the same cause, but may produce different
crash points. The `1` and `2` variants are more minimized and
easier to understand, but they produce different symptoms than
the original case that they may not always spot this issue as
the code evolves.

Bug: 1520442
Change-Id: I3546dba37d0dd2324804ad6c6a408ed162934663
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5251158
Commit-Queue: Koji Ishii <[email protected]>
Auto-Submit: Koji Ishii <[email protected]>
Reviewed-by: Morten Stenshorne <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255473}

- dir-3.html/dir-5.html: These are approximative verifications of overall
  RTL directionality using "covering rectangles". Export them with a
  a specific font in order to make them a bit more robust.
  For dir-5.html we use scripts-spaceafterscript3000.woff and adjust the
  rects accordingly but the test might change later depending on the
  outcome of w3c/mathml-core#217.

- dir-4-ref.html: Removed (the test was removed in bug 1783995).

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1876684
gecko-commit: eb00222e557742d5a6c66534f38345ddf71deaa5
gecko-reviewers: emilio

- mo-movablelimits-dynamic.html: This is the same as the WPT test
  mathml/presentation-markup/operators/mo-movablelimits-dynamic.html

- munderover-accentunder-dynamic/munderover-accent-dynamic: There
  does not seem to be any equivalent tests.  It's possible the tests
  need some refinement to make sure the attributes have an effect on
  this testcase, but for now it's safe to just export them as is.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1876684
gecko-commit: 607f0b698ed2f1632afa2168bb416bfdeb2a5e25
gecko-reviewers: emilio

Much like we suppress most (all?) other block-level scrollframes, see:

  https://searchfox.org/mozilla-central/rev/5c4a45eb17423373ecb71aea9819d41a6231613e/layout/base/nsCSSFrameConstructor.cpp#4392-4394

Otherwise we try to fragment a scrollframe, not good.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1877591
gecko-commit: 24dacb4bb526be404f5617ca9413a4a12c5314b7
gecko-reviewers: dholbert

This patch adds a test, which was accidentally lost while
renaming in PS8 of crrev.com/c/5251158. The content is the
same as the one in PS7.

Bug: 1520442
Change-Id: Ie9b72f63a9560b803f7cd3120c45cc3071302405
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5261043
Reviewed-by: Morten Stenshorne <[email protected]>
Commit-Queue: Morten Stenshorne <[email protected]>
Auto-Submit: Koji Ishii <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255506}

…texts (web-platform-tests#44378)

…platform-tests#44383)

This fixes a bug where dispatching an InvokeEvent with a null invoker
will cause a nullptr exception as it tries to retarget the Invoker based
on the currentTarget.

The fix returns early nullptr if invoker is a nullptr, which also skips
the CHECK_EQ on eventPhase(), as just guarding the Retarget call would
skip to this check which would cause the check to fail if invoker was
retrieved during the bubbling phase.

Bug: 1511341
Change-Id: I6e0e250a47466a502daeb8ab32335ff1521edc48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5260418
Commit-Queue: Joey Arhar <[email protected]>
Auto-Submit: Keith Cirkel <[email protected]>
Reviewed-by: David Baron <[email protected]>
Reviewed-by: Joey Arhar <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255591}

All element reflection IDL attributes must have their attribute name
return true in IsElementReflectionAttribute, or else the attribute and
javascript getter will not be kept in sync. This patch adds the
popovertarget and anchor attributes to that list and also adds a DCHECK
to make sure that when the generated IDL code sets an element attribute,
that attribute is listed in IsElementReflectionAttribute.

Fixed: 1523410
Change-Id: I919153b894884507530b2bb219c4cbf7327780a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5260611
Reviewed-by: David Baron <[email protected]>
Commit-Queue: Joey Arhar <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255605}

The timeout is the likely culprit. If the test flakes again, we should
put the TestExpectations entry back and re-investigate.

Bug: 1430215
Change-Id: I27d450e37920072d04018b1e191b8e7efb1867dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5262097
Commit-Queue: David Awogbemila <[email protected]>
Reviewed-by: Steve Kobes <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255607}

Intent-to-ship:
https://groups.google.com/u/2/a/chromium.org/g/blink-dev/c/S67zJ1AYW2U

Bug: 1466250
Change-Id: Idfa99b35a900440beb53b1c6a7a7af8bee2a66c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5261861
Commit-Queue: Khushal Sagar <[email protected]>
Auto-Submit: David Bokan <[email protected]>
Reviewed-by: Khushal Sagar <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255674}

This reverts commit 572074cb06425797e7e110511db405134cf67e2f.

Reason for revert:
caused regression bug: crbug.com/1521614

Original change's description:
> Remove empty closed paths
>
> As discussed in the github issue,
> whatwg/html#1079, it's generally agreed to
> skip drawing line caps for closed paths. This is a follow up cl of:
> https://chromium-review.googlesource.com/c/chromium/src/+/4864061.
>
> In this cl, it verifies if each closed path is empty, then it removes
> the empty closed subpaths from path. As the subpaths are removed, the
> corresponding line caps are skipped.
>
> Bug: 644067
>
> Change-Id: I14c5c4819a31eb9249d01574ff1b5c60826c3b9e
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4916516
> Commit-Queue: Yi Xu <[email protected]>
> Reviewed-by: Jean-Philippe Gravel <[email protected]>
> Reviewed-by: Justin Novosad <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1247735}

Bug: 644067
Change-Id: I33ecfd76574d6f60e6f8c471a38183f87757e3ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5258624
Reviewed-by: Aaron Krajeski <[email protected]>
Reviewed-by: Jean-Philippe Gravel <[email protected]>
Commit-Queue: Yi Xu <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255711}

This test doesn't actually work since it references an idl file which
isn't defined. I manually verified that the CustomStateSet idl is
already tested by external/wpt/html/dom/idlharness.https.html so there
is no need for this separate test file anymore.

Change-Id: If4aca93159724cdb9e7d007933635a2d55d06f7e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5253030
Commit-Queue: Joey Arhar <[email protected]>
Reviewed-by: Stephen McGruer <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255766}

This patch forbids nested <button>s and <datalist>s to avoid setting
kInSelectMode while we are technically still in a <button> or
<datalist>.

This patch also replaces a call to SetInsertionMode() with
ResetInsertionModeAppropriately() and moves it after processing the end
tag in order to avoid ending up in kInSelectMode when there is not
actually an open <select> tag.

The clusterfuzz crash didn't have a minimal repro but I manually
verified that the crash does not repro with this patch.

Bug: 1511354
Fixed: 1519396
Change-Id: I4358973b36925ea0862f4050f27f804d2676288c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5254124
Reviewed-by: David Baron <[email protected]>
Commit-Queue: Joey Arhar <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255770}

Per spec:

  https://html.spec.whatwg.org/multipage/rendering.html#bidi-rendering

this should be in the UA stylesheet:

address, blockquote, center, div, figure, figcaption, footer,
form, header, hr, legend, listing, main, p, plaintext, pre,
summary, xmp, article, aside, h1, h2, h3, h4, h5, h6, hgroup,
nav, section, search, table, caption, colgroup, col, thead,
tbody, tfoot, tr, td, th, dir, dd, dl, dt, menu, ol, ul, li,
bdi, output, [dir=ltr i], [dir=rtl i], [dir=auto i] {
  unicode-bidi: isolate;
}

To avoid breakage, I just added the elements, and not the [dir]
related rules, nor did I change the <bdo> rules.

Firefox and WebKit are both making the same change:
https://bugzilla.mozilla.org/show_bug.cgi?id=1874033
https://bugs.webkit.org/show_bug.cgi?id=267887

The stylesheet change interacts with the code at [1], and that code
also handles some of the cases such as [dir=auto] and bdi/bdo.
I will clean up some of the code at [1] in a followup CL.

[1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/html_element.cc;l=344-363;drc=20fecf94cc2226674dfefd698e96d8d44485b19c

Fixed: 1520671
Change-Id: Icaa32061efc59d963942b0629327bb596ac224ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5240082
Auto-Submit: Mason Freed <[email protected]>
Reviewed-by: David Baron <[email protected]>
Commit-Queue: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255819}

When the canvas has to be presented while layers are opened, we cannot
present the layer content, but we can present any painting that happened
before the top most layer was opened. To do so, the recording has to be
split into two parts: a main recording and a side recording. The side
recording holds the content of all nested layers in one single
recording. When the top most layer is closed, the content of the side
recording is written to the main recording.

Bug: 1484741
Change-Id: Id32412819c0395edd501243b2ccead30ebc0b674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5113500
Commit-Queue: Jean-Philippe Gravel <[email protected]>
Reviewed-by: Fernando Serboncini <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255834}

The change adds MP4 mime type to the relevant tests
on the MediaRecorder tests where the test reached to the
muxer level.

There is a bug that block the change of 'PMediaRecorder-peerconnection.https.html', which will be handled with
bug fix of 1523375.

Bug: 1072056
Change-Id: Ie3c2c306bb454e1eb8914047137c6a5844bcdfdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5250746
Commit-Queue: Sunggook Chue <[email protected]>
Reviewed-by: Hirokazu Honda <[email protected]>
Reviewed-by: Dale Curtis <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255836}

…s#44345)

Adds tests for `race-network-and-fetch-handler`, which is the service
worker static routing API's router source option.

This tests check the case when the network request wins and the fetch
handler wins the race respectively, both for the main resource and
subresource.

Bug: 1519727
Change-Id: I19fe304c294f64d99d08c76be113a41d726b8d52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5256919
Commit-Queue: Shunya Shishido <[email protected]>
Reviewed-by: Yoshisato Yanagisawa <[email protected]>
Reviewed-by: Kouhei Ueno <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255046}

Co-authored-by: sisidovski <[email protected]>

…m-tests#44372)

Only in cases where there is not a single pointer event registered on a page, blink may entirely optimize out EventDispatch steps, since there are no observers anyway.  This optimization should not normally be detectable.

However, the Event Timing API still measures these events and reports them to the performance timeline.  Because the EventDispatch steps are where we assign EventTarget to Event objects, the Event Timing API was effectively missing the target value whenever we skipped this step.

This patch plumbs the original HitTest target which we fall back to under such situations.

Bug: 1367329
Change-Id: Icf21e6103c98261e9f6e88cef1ac09f3a683751b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5246848
Commit-Queue: Michal Mocny <[email protected]>
Reviewed-by: Aoyuan Zuo <[email protected]>
Reviewed-by: Christian Biesinger <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1255634}

Co-authored-by: Michal Mocny <[email protected]>

…orm-tests#43013)

Nightly-only for now waiting on CSSWG discussion.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1868316
gecko-commit: 6fdde7dce00345bc568706b0cf7de521b91ba75a
gecko-reviewers: jfkthame

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1144434
gecko-commit: e6b6322cf7a97bfef714c3e1c901937546fb740f
gecko-reviewers: TYLin

…ts#44361)

* Add null-check to aria_utils verifyLabelsBySelector

Before this commit, verifyLabelsBySelector calls test_driver.get_computed_label
and then does string-manipulation on the result. For some reason, this
get_computed_label invocation returns null in Firefox, and so the
string-manipulation causes a JS exception to be thrown, which makes for awkward
test failure results.

Let's just explicitly assert that the result is not-null, to make that
expectation clearer and to give a cleaner test-failure in cases where it is
unexpectedly null.

Before this CL, in the renderer, registered routers are not evaluated if
there is no fetch handler in the service worker. This is critical and
introduces unexpected behavior for the static routing API, because
developer may only use static routing API, that doesn't guarantee the
fetch handler existence.

This CL add the new boolean field, `need_router_evaluate` to
ControllerServiceWorkerInfo mojo interface. The renderer side use this
field to decide whether it involves ServiceWorkerSubresourceLoader or
not.

Bug: 1511459
Change-Id: I88e09900931a149c78cc4f25015fa5a5b1ffd62c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5252809
Reviewed-by: Yoshisato Yanagisawa <[email protected]>
Reviewed-by: Takashi Toyoshima <[email protected]>
Commit-Queue: Shunya Shishido <[email protected]>
Reviewed-by: Minoru Chikamune <[email protected]>
Reviewed-by: Kouhei Ueno <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256065}

This tests color of `<mtext href>` links. Although links were mentioned
in a previous draft of MathML Core, they have been removed from the
current version and adding them back is pending consensus. However,
upstream WPT still contains tests for MathML links so it makes sense
to have all of these tentative tests.

This commit exports `link-001.html` as a tentative mismatch reftest
with proper renaming (note that the `<link rel="mismatch">` refers to a
non-existent `link-color-001-ref.xhtml` file).

Similarly, all the existing tests assuming support for `href` are
renamed as 'tentative' tests.

Finally, we also remove a few annotations from bug 1798871.

There is no behavior change.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1876684
gecko-commit: 5ec8a1a095532086defe3180d8ca1d16cd53df20
gecko-reviewers: emilio

- mpadded-1/2/3.html, mpadded-1-2.html: These are testing visual
  rendering of two nested mpadded elements with basic attribute values
  that are accepted by MathML Core.

- mpadded-4.html: This is testing mpadded attribute with pseudo
  units, which are not supported by MathML Core, so convert to
  internal WPT test.

- mpadded-5/6: These are testing negative values of some mpadded
  attributes whose interpretation or support is unclear in MathML
  Core. So convert to internal WPT tests for now.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1876684
gecko-commit: a55c77e16ea8c476eee487f52739314d54a3c39a
gecko-reviewers: emilio

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

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

…platform-tests#44395)

The test that "credential" will be a DOMString turned out to be
a failure because any Javascript object can be converted to the
string "[Object object]".

The referenced part of the specification isn't there any more.

Bug: None
Change-Id: Ie6a08a24f76e7a895517feef587ff31ecfe2fdac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5266622
Reviewed-by: Guido Urdaneta <[email protected]>
Commit-Queue: Harald Alvestrand <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256182}

Signed-off-by: syvb <[email protected]>

The only time we need hidden nodes is when they are part of a
label or description. This CL keeps track of whether a given node
has ever been part of a label or description. If the node is hidden,
it removes it from the tree unless it's needed for a label/description.

In combination with CL:4852390, which removes hidden line breaks,
reduces the time spent in serialization and deserialization by
massive amounts in tests that involve heavy usage of hidden subtrees.
For the specific results, see:
https://docs.google.com/spreadsheets/d/1ozLJMRT32yIxE0ja0rDhdZPb76hQtDd0klcRcR_uWYU/edit?pli=1#gid=0
This will make a significant difference in web apps with panels,
chats, slides, etc. where a significant percentage of the content
is hidden.

Bug: 1448706, 1353788
Cq-Include-Trybots: luci.chromium.try:fuchsia-x64-accessibility-rel,linux-blink-web-tests-force-accessibility-rel
Change-Id: I1b0de1d9b6f037c107efd3ca93c073382fd0ece1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4574033
Commit-Queue: Aaron Leventhal <[email protected]>
Reviewed-by: Chris Harrelson <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256230}

Checkboxes support validity via the required attribute and the other
browsers support :user-valid/:user-invalid on them. The existing
:user-valid/:user-invalid machinery only works on text fields, so this
patch adds some code to checkboxes to make them work as well.

Fixed: 1521781
Change-Id: I91309f36348470db5b1c706b519e6303e5deeab1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5258739
Commit-Queue: Joey Arhar <[email protected]>
Reviewed-by: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256264}

As per spec, sourceURL / sourceFunctionName / sourceCharPosition
Amended existing test.

Bug: 1523675
Change-Id: Ic3bb8df05bb822fa8b56990e2696d67324b4763f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5250540
Reviewed-by: Ian Clelland <[email protected]>
Reviewed-by: Rick Byers <[email protected]>
Reviewed-by: Michal Mocny <[email protected]>
Commit-Queue: Noam Rosenthal <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256409}

This includes tests to confirm size/cols/rows are not presentational hints.

Issue: whatwg/html#6807

…ercentages inside calc() in background-position longhands.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1874606#c3 (and the
test is self-explanatory, it's just a copy of
background-position-negative-percentage-comparison.html but with the
longhand expanded).

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874606
gecko-commit: c133f145c3444956eaacebff4066a0141a971af1
gecko-reviewers: layout-reviewers, jfkthame

This is kind of a wallpaper, but I think it's sound, read below.

The reason this is asserting is that MathML in particular has some odd
frame re-parenting going on (see
nsCSSFrameConstructor::FlushAccumulatedBlock).

That means that our assert in DepthOrderedFrameList is not really
holding depending on when you add or remove the frame from the list.

However this is not a problem in practice, at least for container
queries, because anonymous frames that can wrap mathML cannot be
containers themselves.

I need to figure out what to do with that assert, but given it's useful
for the other users of DepthOrderedFrameList, I think we should take
this for now.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1878188
gecko-commit: 7146c4efa63b2195fb331439048c4e1def420323
gecko-reviewers: fredw

…continueRequest

Depends on D199749

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: 2e55faaccd8265b6e48fb904d0104dc9ebdc6a84
gecko-reviewers: webdriver-reviewers, Sasha

…ontinueRequest

Depends on D199750

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: e088bd5cef05706254aac5844de407a74a2b3bd3
gecko-reviewers: webdriver-reviewers, Sasha

…continueResponse

Depends on D199751

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: 9636ddc3709af33bb67d228ea6022a8257c2d1b2
gecko-reviewers: webdriver-reviewers, Sasha

…ontinueResponse

Depends on D199752

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: cf600694c18f22e5cece13d493171124eff5d04d
gecko-reviewers: webdriver-reviewers, Sasha

Depends on D199753

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: c2eb34cf5007303cf4643d671d7be9e287d0e9b9
gecko-reviewers: webdriver-reviewers, Sasha

Depends on D199754

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: 3884f0a38e09c6f16ef962a3b1db5623c659b4ff
gecko-reviewers: webdriver-reviewers, Sasha

…network tests

Depends on D199755

Adds test helpers to easily create header and cookie header objects

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874206
gecko-commit: a3f956419067fa1803aa9210eb8252a3fc3daefa
gecko-reviewers: whimboo, webdriver-reviewers

This removes `tentative` from Web Locks tests which all three engines are passing. A couple of exceptions from https://wpt.fyi/results/web-locks?label=experimental&label=master&aligned

* clientids: The test follows the spec, I think this is a Chrome bug. (https://w3c.github.io/web-locks/#dom-lockmanager-request, the use of environment's id)
* signal: A couple of WebKit failures because of lack of AbortSignal custom reason support.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1878367
gecko-commit: 4235c5a3b4ac51348c29bfd3bf8e371b67b982c6
gecko-reviewers: smaug

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1267079
gecko-commit: 391d1d3ba83e86e6535622a39119feb8f2b6a2f0
gecko-reviewers: emilio, TYLin

* Fix reflection tests wrt valueOf

Without a toString:null in test values that are objects
with a valueOf method, the DOM attribute would actually
be set to "[object Object]" without ever calling the
valueOf method (effectively turning those tests into
behaving exactly the same as the {"test": 6} ones).

Most existing tests were passing because the implemented
algorithms would actually compute a WRONG expected value.
The only test that doesn't compute the expected value
("double") won't actually run because all reflected IDL
attributes of type "double" have custom getters.

Fixes web-platform-tests#44315

* Fix reflection tests wrt -0 for "double" attributes

Setting -0 to the IDL attribute will set the DOM
attribute to "0" (per ECMAScript's ToString, from the
rules for the the best representation of a number as
a floating point number), and the rules for parsing
flowting-point number values won't ever turn that "0"
into a -0 value.

This test value is never actually being used though,
as all the reflected attributes of type "double" have
custom getters.

* Add a few more reflection tests around whitespace for numeric types

Specifically leading non-ASCII whitespace following leading
ASCII whitespace (should be rejected), and trailing non-ASCII
whitespace (should be ignored)

* Add a few more numeric values to reflection tests

Specifically "+" and "-" to exercise all possible code
paths of failures.

* Add exponential notation to reflection tests of double values

* Implement "limited double" in reflection tests

* Implement the reflect algorithm for doubles

This should make it easier to extend tests with more values.

An agreed upon proposal[1] by the CSS working group specifies that
where multiple scroll snap targets are visually equally aligned,
scroll containers should give priority to focused elements.
Blink did this for programmatic scrolls but not for user scrolls.
This patch prioritizes focused elements for both types of scrolls
by relying on a bit in SnapAreaData.

[1]w3c/csswg-drafts#9622

Bug: 1523819
Change-Id: I81e2aaf0845e9763abb463a960614beb37b05a8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5255777
Reviewed-by: Steve Kobes <[email protected]>
Commit-Queue: David Awogbemila <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256790}

…ver_util.py

The CORS logic present in direct-from-seller-signals.py is identical to
that needed for other web platform tests. Moving this logic into a
common function available to the endpoints needed for those other web
platform tests prevents duplication. This change also attempts to match
the style of the Python test server in new and existing code.

Change-Id: Ia3db1e263e3e4b1e6b09bfa3408dd905a83ea44b
Bug: 40275797
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5269747
Commit-Queue: Orr Bernstein <[email protected]>
Reviewed-by: Matt Menke <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256845}

… interface

Explainer PR: WICG/shared-storage#130

Bug: 1218540
Change-Id: I7dffe4e026a6ebf4e6705b1df43e2baf01dadb12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5209512
Commit-Queue: Yao Xiao <[email protected]>
Reviewed-by: Dominic Farolino <[email protected]>
Reviewed-by: Cammie Smith Barnes <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256903}

The referring URL as computed by the referrer policy for the prefetch
request was incorrectly being used to determine whether a prefetch was
cross site. This value is only meant to be used for the prefetch
request. The omission of the URL made it look like a cross site
prefetch, so the cookie eligibility check was applied.

We now use the initiating origin to determine whether a prefetch is
cross site.

Bug: 1524338
Change-Id: Id154effae55c539fff7cd733327fc9029c53b03a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5263133
Commit-Queue: Kevin McNee <[email protected]>
Reviewed-by: Liviu Tinta <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256905}

This change adds support to observe out of viewport targets inside
scrollable same origin iframes using intersection observers with
scrollMargin, by crossing the iframe boundary when collecting
intermediate scrollers.

R=szager

Bug: 1503290
Change-Id: Iaf5482a67e8eb37000d54fb9529df5c16f86e644
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5240906
Reviewed-by: Stefan Zager <[email protected]>
Commit-Queue: Traian Captan <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1256994}

Now that the HTML parser allows <button> and <datalist> in <select>,
this patch modifies the UA shadowroot of <select> to slot the <button>
and <datalist> and render them. If a <button> is provided with no
<datalist>, then the native popup is used. If a <datalist> is provided
with no <button>, then the native button is used.

Bug: 1511354
Change-Id: I36f88f73949aa2cba502231ed2d68c1738e47946
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5230929
Auto-Submit: Joey Arhar <[email protected]>
Reviewed-by: Mason Freed <[email protected]>
Commit-Queue: Joey Arhar <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257004}

Declarative shadow DOM is standard [1] and implemented in all
modern browsers. This removes a polyfill that isn't needed in WPT
any longer.

[1] https://html.spec.whatwg.org/multipage/scripting.html#attr-template-shadowrootmode

Bug: N/A
Change-Id: Ie9bfdf24f75901cf9a476844a76065e5a18a6815
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5263643
Auto-Submit: Mason Freed <[email protected]>
Reviewed-by: Joey Arhar <[email protected]>
Commit-Queue: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257013}

…eb-platform-tests#44424)

This allows vendors to override expectations at runtime via
browser-specific result converters. Instead of constructing
`(Subtest)Result`s directly, executors should use the newly introduced
`Test.make_{subtest_,}result()`, which have the same signatures but
default to passing through the testloader-read expectations.

This is a pure refactor; no functional changes intended.

Successor to: web-platform-tests#44134 (comment)

This CL migrate Web Serial MojsJS based tests to internal folder
temporary. We will move it back once Web Serial Testing specification
for test-only interface is defined.

Bug: 1524403
Change-Id: I75323dfe2a649348e23c333e1a635cf8cc9ba806
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5259047
Reviewed-by: Matt Reynolds <[email protected]>
Commit-Queue: Alvin Ji <[email protected]>
Reviewed-by: Alvin Ji <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257126}

…rContext

Depends on D200019

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874918
gecko-commit: 9958e50aa342f1417ae85b1ceed8a11d5864d521
gecko-reviewers: webdriver-reviewers, Sasha

…texts are closed

Depends on D200023

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874918
gecko-commit: 4be6b1980ac25cdf37cea10a1b246151b6646811
gecko-reviewers: webdriver-reviewers, whimboo

* add zstd tests and separate into folders

* add bad input tests and make window size test tentative

* add https to bad input test

…royed user context tests

Depends on D200024

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874920
gecko-commit: 0237b0c99f398a9c4ac048bbdf029d8bc16e3771
gecko-reviewers: webdriver-reviewers, whimboo

Depends on D200032

This should ensure good coverage of the user_context field

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874920
gecko-commit: 8a66a3b89c40f8a8f3195f6a92c0c3d2af587b21
gecko-reviewers: webdriver-reviewers, whimboo

Depends on D200181

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874920
gecko-commit: 1c00d395406fc5b994ce1a16d8625ba85d57a8bd
gecko-reviewers: webdriver-reviewers, whimboo

… internals.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1877025
gecko-commit: 40bac1b10006b24580bad57de6cf5efb2415ad67
gecko-reviewers: peterv, dom-core

Now part of the spec draft

Bug: 40279608
Change-Id: I35546256c8460bfa46d1b9b7607e008d069cbd6d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5272498
Reviewed-by: Anders Hartvoll Ruud <[email protected]>
Auto-Submit: Rune Lillesveen <[email protected]>
Commit-Queue: Rune Lillesveen <[email protected]>
Commit-Queue: Anders Hartvoll Ruud <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257259}

Per UAX#9 L1, any spaces that after line breaking would fall logically
at the end of a line must be reset to the paragraph's initial
embedding level, regardless of the embedding level of those spaces in
the paragraph. Until now, Blink only had partial support for this.

The reason this was hard to implement in Blink is because the
direction of text is computed in a per-paragraph level, splitting the
text into items with a given direction and embedding level. Those
items are then split into item results when line breaking, but item
results must have the same direction as the item.

As part of line breaking, some item results are produced which only
have trailing spaces. The partial support, implemented in
crrev.com/c/2505486, consisted of marking these results with the
`has_only_trailing_spaces` flag, and using this flag to distinguish
them when reordering the item results.

This patch builds on top of that partial fix by adding a final
processing step to line breaking, which splits item results so that
trailing spaces (with a different embedding level as the paragraph)
are split into its own item result, and by marking all trailing spaces
item results as `has_only_trailing_spaces`.

This also fixes bug 1514753, where having a item result with non-base
direction which had logically trailing spaces was causing the text
(rather than the spaces) to hang, because
`LineInfo::ComputeTrailingSpaceWidth` assumed that UAX#9 L1 held.

This patch also modifies some existing WPT tests to make them use a
monospace Arabic webfont (since it's not guaranteed that all OS's have
one), and by changing the widths slightly to work around bug 1409445.

Bug: 316409, 1514753
Change-Id: I1eb751b457d413b5099dad8f95badba9a1b3e5fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5199988
Reviewed-by: Koji Ishii <[email protected]>
Commit-Queue: Andreu Botella <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257309}

This CL implements the semantics specified in
https://wicg.github.io/observable/#dom-observable-foreach.

See WICG/observable#105.

For WPTs:
Co-authored-by: [email protected]

[email protected]

Bug: 1485981
Change-Id: I61344bad7fa4bac65146e1305a376fc1f5e55dc3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5249869
Reviewed-by: Mason Freed <[email protected]>
Commit-Queue: Dominic Farolino <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257328}

…in different root

Users of `Selection` assume that `nsRange` instances are ranges in the
corresponding document.  However, `Selection` may keep storing ranges in
the different root only when the range is updated.  I think that no spec
defines this behavior, but Chromium makes `RangeUpdateScope` delete ranges
which are in different root after the range is updated [1].  Let's follow
this behavior for compatibility and keeping the assumption of `Selection`
users.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1878191
gecko-commit: cfc39990144c47c50d76e747f22987360634d6f8
gecko-reviewers: smaug, jjaschke, dom-core

Per web-platform-tests#43574, we should
follow the shortest serialization principle for `transition` shorthand.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1878758
gecko-commit: edd89a13946a1e81af2699a6a15969957c86a41e
gecko-reviewers: zrhoffman

…ctually needed to break the text.

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

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

Somehow we ended up throwing if it's explicitly denied. Now it throws error with the default permission too.

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1874958
gecko-commit: ab5b008e36a4742d737a89c8cbfc1a69e2b76456
gecko-reviewers: asuth

Explainer PR: WICG/shared-storage#130

How:
- Introduce sharedStorage.createWorklet() method. In this patch,
we still restrict the script to same origin. Ultimately, we will
support cross-origin script/worklet (for the createWorklet() API).
- Also, move the document service Remote to a window supplement
class: This is a forward-looking change (e.g. it'll enable
constructing the worklet via `new SharedStorageWorklet()` / not
needing to exist along with the `sharedStorage` object, although
this isn't in the current proposal).

Bug: 1218540
Change-Id: I5bf64bdf6648a76875748b194e5dbceeb1400624
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5209102
Reviewed-by: Dominic Farolino <[email protected]>
Reviewed-by: Avi Drissman <[email protected]>
Commit-Queue: Yao Xiao <[email protected]>
Reviewed-by: Cammie Smith Barnes <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257412}

When the active EditContext's associated element is a <canvas>, we
fail to fire the textudpate event when the user hits backspace/delete.

The reason is that for these keystrokes, EnabledInEditableText is
used to determine whether the command is enabled, and this includes
a check that the selection is contained in the focus. For <canvas>
this will never be the case because <canvas> cannot contain selection.

Fix this by always treating the command as enabled if there is an
active EditContext, since an EditContext should always have the
opportunity to handle these commands.

Update some existing text input and text deletion tests to run for
<canvas> in addition to <div>.

Bug: 1517103, 999184
Change-Id: Id8d4509ed6b22a4516d9bfa2c4a05b234eea78de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5251988
Reviewed-by: Anupam Snigdha <[email protected]>
Reviewed-by: Koji Ishii <[email protected]>
Commit-Queue: Dan Clark <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257455}

We need to make sure that we create enough pages to contain tall
monolithic out-of-flow positioned descendants, including any overflow
inside of them.

Similar support for in-flow elements was added in CL:5029779, where we
at the same time stopped synthesizing missing pages after layout, but
instead started to trust layout. However, that was premature, since
out-of-flow positioned descendants of course need special treatment.

Bug: 41496759
Change-Id: If52a4b1ad50ec55dbdabc6456b47a299404f7d25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5272404
Reviewed-by: Alison Maher <[email protected]>
Commit-Queue: Morten Stenshorne <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257469}

* allow old headless mode for chrome

While Wptrunner's '--headless' means the new headless mode, allow
passing binary arg '--headless' to chrome directly to enable the
old headless mode

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1876541
gecko-commit: a7519f7b264ccb39d5a6f9ff1f9371f3febedebf
gecko-reviewers: TYLin

…network/continue_request/invalid.py

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1879006
gecko-commit: 2c96ad2803366505f65dc66c1ffc3eb96009476c
gecko-reviewers: webdriver-reviewers, whimboo

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

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1302722
gecko-commit: 1118131d963c7a00bb60693f1c4c15b3b4b40d17
gecko-reviewers: jfkthame, emilio

HTMLLabelElement::DefaultEventHandler does not currently call up to
HTMLElement::DefaultEventHandler in many cases. This patch makes sure
that HTMLLabelElement always calls up to HTMLElement, which makes
<label>s in <button>s work.

WebKit's HTMLLabelElement already does this in all branches of
HTMLLabelElement::defaultEventHandler since 2017:
WebKit/WebKit@fec9c1d
WebKit/WebKit@b9bad31

Fixed: 1523168
Change-Id: Ib9d0a63befbb930b9595bcc89fb5955050c97b2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5260750
Commit-Queue: Joey Arhar <[email protected]>
Reviewed-by: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1257674}