845df881fa2cb807866ed3f44fb0229cd88014b1: Bug 1760772 [wpt PR 33297] - Update who has access to wpt.fyi domain and GCP, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 24 Mar 2022 12:18:49 +0000 - rev 687318
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760772 [wpt PR 33297] - Update who has access to wpt.fyi domain and GCP, a=testonly Automatic update from web-platform-tests Update who has access to wpt.fyi domain and GCP (#33297) -- wpt-commits: 2f8b60ab5fe18d9b1511ffd149922a379e425307 wpt-pr: 33297
07994bf19a7978f015146667081b030b23d01d4b: Bug 1694391 [wpt PR 33258] - [Gecko Bug 1694391] [webdriver-client] Add browsing context module to WebDriver BiDi client., a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 24 Mar 2022 12:17:02 +0000 - rev 687317
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1694391 [wpt PR 33258] - [Gecko Bug 1694391] [webdriver-client] Add browsing context module to WebDriver BiDi client., a=testonly Automatic update from web-platform-tests [webdriver-client] Add browsing context module to WebDriver BiDi client. Differential Revision: https://phabricator.services.mozilla.com/D140807 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1694391 gecko-commit: dcfe0ab9025df8a3e6a2dd70d9afa7f12e14708d gecko-reviewers: jgraham, webdriver-reviewers, jdescottes -- [wdspec] Added web-platform tests for browsingContext.getTree command. Differential Revision: https://phabricator.services.mozilla.com/D140725 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1694391 gecko-commit: dd61f79731b96cb657dd292147d5ab484a9e6324 gecko-reviewers: webdriver-reviewers, jgraham, jdescottes -- Fix for flake8 failures -- wpt-commits: 211a4b84500e335a52406afed88373ba13b1eb0f, 228559b5644d05a3ec4aba4463adc163fc307065, 62a2f2272444047a340dfb55cc7a017c50c40bc8 wpt-pr: 33258
d3be3b6a93dd03934189fcdfb3bd9a34b0b5f3ec: Bug 1760817 [wpt PR 33301] - [FlexNG] Add github links to tests, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 24 Mar 2022 12:12:05 +0000 - rev 687316
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760817 [wpt PR 33301] - [FlexNG] Add github links to tests, a=testonly Automatic update from web-platform-tests [FlexNG] Add github links to tests Add the following github link to the relevant flex tests: https://github.com/w3c/csswg-drafts/issues/6056#issuecomment-951767882 Bug: 660611 Change-Id: I43548a9caa2784e8badb2c0d357b00c745136c25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3541545 Auto-Submit: Alison Maher <almaher@microsoft.com> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#983883} -- wpt-commits: fa2a2e69a1881a94580d4b0422f1a411e26bfe8c wpt-pr: 33301
c2556e068e90f32801c670b7f0dcfef6b2c2fa22: Bug 1760729 [wpt PR 33292] - Reflect aria-invalid as ariaInvalid property, a=testonly
Mason Freed <masonf@chromium.org> - Thu, 24 Mar 2022 12:11:58 +0000 - rev 687315
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760729 [wpt PR 33292] - Reflect aria-invalid as ariaInvalid property, a=testonly Automatic update from web-platform-tests Reflect aria-invalid as ariaInvalid property The ARIAMixin IDL contains ariaInvalid [1], but Chromium was not reflecting this property. This CL adds reflection plus some testing. [1] https://w3c.github.io/aria/#ARIAMixin Fixed: 1305421 Change-Id: Ifecdec95c111bf71d7eb307ea6490473f3d12917 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3541417 Auto-Submit: Mason Freed <masonf@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#983863} -- wpt-commits: 45e0ae17fd99f5f53655d3ff895ddb667f46eac5 wpt-pr: 33292
b1abc2c4a8656c6d8067e4d40ed34f3f02b7fcd6: Bug 1746074 [wpt PR 32068] - Create property tree nodes for will-change only when relevant property has will-change., a=testonly
L. David Baron <dbaron@chromium.org> - Thu, 24 Mar 2022 12:11:53 +0000 - rev 687314
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1746074 [wpt PR 32068] - Create property tree nodes for will-change only when relevant property has will-change., a=testonly Automatic update from web-platform-tests Create property tree nodes for will-change only when relevant property has will-change. Prior to this change, will-change: transform, opacity, filter, or backdrop-filter would cause the creation of property tree nodes (in both the paint property tree and the cc property tree) for all of them (though only a single effect property node for both opacity and backdrop-filter). With this change, will-change: transform only causes the creation of a transform node (in the transform tree), will-change: filter only causes the creation of a filter node (in the effect tree), and will-change: opacity or backdrop-filter only causes the creation of an effect node (in the effect tree). However, *if* the nodes are created by something else, the presence of a different will-change still causes any node that is created in the paint property tree to be composited (i.e., created in the cc property tree). This provides the basis on which we can separate the transform node into multiple transform nodes, for efficient implementation and animation of individual transform properties, without causing a performance regression. Earlier versions of this CL (prior to the change that kept nodes being composited for an unrelated will-change) caused the test external/wpt/css/filter-effects/effect-reference-feimage-002.html to start failing (in the same way as -001 and -003) because the filter effect is no longer composited. It creates a copy of the test as -004 with will-change: filter rather than will-change: transform that continues to have a composited filter effect node and thus continues passing even with that earlier change. This test still seems worth adding despite no longer strictly being needed. Bug: 900241 Change-Id: I18efc630668ea7eac2a8c0a0417b766762e71d9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3328730 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: David Baron <dbaron@chromium.org> Cr-Commit-Position: refs/heads/main@{#983821} -- wpt-commits: b94dd9d75160c92f7e444458770e2586cf12d197 wpt-pr: 32068
10e34d02a17bc7d3aeccb9a1fd3a78c6996de629: Bug 1760822 [wpt PR 33244] - Use httpx instead of requests in tests, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 24 Mar 2022 12:11:47 +0000 - rev 687313
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760822 [wpt PR 33244] - Use httpx instead of requests in tests, a=testonly Automatic update from web-platform-tests Use httpx instead of requests in tests (#33244) Following https://github.com/web-platform-tests/wpt/pull/33113, there was only one minor use of requests left in test code. requests is still a depdendency of a lot of code under test, but this at least simplifies requirements_tests.txt. -- wpt-commits: 4dd5d8cb8d775c7f7e7b36b143d2b21a3afcbbfd wpt-pr: 33244
920b070ad704eb8c6cc42a3aac1cbb8351a0168d: Bug 1760796 [wpt PR 33299] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 15:38:09 +0000 - rev 687312
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760796 [wpt PR 33299] - Update wpt metadata, a=testonly wpt-pr: 33299 wpt-type: metadata
a2d47660740616ac1a4b43d13b0febe0c502ec89: Bug 1760796 [wpt PR 33299] - Add back idlharness.js tests after split from HTML, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 24 Mar 2022 12:11:37 +0000 - rev 687311
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760796 [wpt PR 33299] - Add back idlharness.js tests after split from HTML, a=testonly Automatic update from web-platform-tests Add back idlharness.js tests after split from HTML (#33299) The tests were removed with a @webref/idl sync: https://github.com/web-platform-tests/wpt/pull/32965 Add back the tests and make some other changes to adapt to the split. -- wpt-commits: 7a15a1905e54107d0ddca296ea8560ca2adc6c99 wpt-pr: 33299
43da3ec00d2cc58001db9b123712ed0d87518307: Bug 1760717 [wpt PR 33290] - [tables] Fix crash when recomputing baselines., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Thu, 24 Mar 2022 12:11:28 +0000 - rev 687310
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760717 [wpt PR 33290] - [tables] Fix crash when recomputing baselines., a=testonly Automatic update from web-platform-tests [tables] Fix crash when recomputing baselines. When we use the layout cache-slot for recomputing the row baselines this can place the layout-tree in an inconsistent state. We have two options to fix this, either use the measure slot (however this may miss - and potentially also leave tree in inconsistent state?) This fix using the disable-side-effects scope to prevent setting invalid layout results on the tree. Bug: 1308047 Change-Id: Ic43707ff7704485838e21668aed3c41fd048916a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3540916 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#983790} -- wpt-commits: 9bf7fbbe034197810648a18ddce13bfae51296a0 wpt-pr: 33290
427c37337fac9b4512e580e9d023f74f659cf7e1: Bug 1760801 [wpt PR 33066] - Output Chromium log on `shutdown`, not `suite_end`, a=testonly
Jonathan Lee <jonathanjlee@google.com> - Thu, 24 Mar 2022 12:11:23 +0000 - rev 687309
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760801 [wpt PR 33066] - Output Chromium log on `shutdown`, not `suite_end`, a=testonly Automatic update from web-platform-tests Run logger.suite_{start,end} before or after all repetitions, not each repetition -- Log Chromium tests results on shutdown, not suite_end -- Fix Chromium formatter tests * Ensure `shutdown` is called after each test to write a final message. * Reset logger state before use. Logger state is normally persisted globally. * Add Chromium formatter test to check the output of a test suite run multiple times. -- Convert logger construction to pytest fixture and reset state after use, not before -- wpt-commits: 68a3f64b100ec5a55a4124f6285aea0d0f79ba4c, fd9207f772cffd40ff520c5693f473bd7862e069, e2579a9f1e8f36aae9bce8659cf773f326b4a5e9, ea42c8e4cb9367ccfcad6fcfa1e98a4da5f409ed wpt-pr: 33066
3599c85f68b2dbec6e0b6ca022df676d0d0c87a8: Bug 1760798 [wpt PR 33230] - Ensure that the call to kill the WebDriver always returns within a deadline, a=testonly
Carlos Alberto Lopez Perez <clopez@igalia.com> - Thu, 24 Mar 2022 12:11:17 +0000 - rev 687308
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760798 [wpt PR 33230] - Ensure that the call to kill the WebDriver always returns within a deadline, a=testonly Automatic update from web-platform-tests Ensure that the call to kill the WebDriver always returns within a deadline There is a bug on mozprocess ProcessHandler.kill that may cause it to hang when the process to be killed has daemonized childs. To avoid this situation, pass the timeout parameter to ProcessHandler.kill to ensure it always returns within it. So wptrunner can continue executing other tests and the whole test suite doesn't hang. Fixes: https://github.com/web-platform-tests/wpt/issues/33186 -- wpt-commits: ce18772029ded0d458d0cd600f1a58bb0c422d72 wpt-pr: 33230
1e3cc8383fa7a8d9d2a59841bf61622c08fa754f: Bug 1756976 [wpt PR 32965] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 14:32:17 +0000 - rev 687307
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1756976 [wpt PR 32965] - Update wpt metadata, a=testonly wpt-pr: 32965 wpt-type: metadata
e3108060825b146690df9b2a796a0109ddec835c: Bug 1756976 [wpt PR 32965] - Sync interfaces/ with @webref/idl 3.4.0, a=testonly
github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> - Thu, 24 Mar 2022 12:10:55 +0000 - rev 687306
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1756976 [wpt PR 32965] - Sync interfaces/ with @webref/idl 3.4.0, a=testonly Automatic update from web-platform-tests Sync interfaces/ with @webref/idl 3.4.0 (#32965) -- wpt-commits: ce632cb42b021f7f346a3edb9c805aa3f3f9a7b4 wpt-pr: 32965
dd80bfa3e93ca06f3b75c65388cc9325f0d9c0aa: Bug 1754523 [wpt PR 32776] - More incremental style updates., a=testonly
Steinar H. Gunderson <sesse@chromium.org> - Thu, 24 Mar 2022 12:10:38 +0000 - rev 687305
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1754523 [wpt PR 32776] - More incremental style updates., a=testonly Automatic update from web-platform-tests More incremental style updates. If we have an existing computed style on a given element, and the only changes have been mutations of independent properties on the element's inline style we can often reuse the old computed style and just reapply the element's inline style on top of it. This allows us to skip collecting elements and computing the full cascade, which can be a significant win when animating elements via inline style from JavaScript. Speeds up the MotionMark “multiply” test by 20–27%, depending on platform. Change-Id: I78f1f30440cdb574dba9012b28fe27b1f60ef89f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3412160 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Steinar H Gunderson <sesse@chromium.org> Cr-Commit-Position: refs/heads/main@{#983777} -- wpt-commits: ea57816ad57eb00d336c7942053376928bc2638c wpt-pr: 32776
275bb94ede2fbe8a268237efa70286c964c3614c: Bug 1760595 [wpt PR 33282] - [@container] Typed OM tests for container-name, a=testonly
Rune Lillesveen <futhark@chromium.org> - Thu, 24 Mar 2022 12:10:32 +0000 - rev 687304
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760595 [wpt PR 33282] - [@container] Typed OM tests for container-name, a=testonly Automatic update from web-platform-tests [@container] Typed OM tests for container-name This is currently broken in the same way animation-name is broken. Added same FIXME as animation-name test has. Bug: 1213890 Change-Id: I1d09e47d83d995a926bc9a6e62633b252198dd0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3540163 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#983772} -- wpt-commits: 0ecd612cb54f02a52447b5630f1388b8d62eec21 wpt-pr: 33282
45669fabd9fff67357a47dc0d764354df8ebb182: Bug 1760603 [wpt PR 33284] - Check writing direction when painting column rules., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 24 Mar 2022 12:10:27 +0000 - rev 687303
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760603 [wpt PR 33284] - Check writing direction when painting column rules., a=testonly Automatic update from web-platform-tests Check writing direction when painting column rules. Rather than deducing it from the column offsets relatively to each other, use computed style to check writing-mode and direction. We'd fail a DCHECK if we ended up with saturated LayoutUnit values for vertical-rl multicol containers (because we'd incorrectly think that writing mode was horizontal). Bug: 1308191 Change-Id: I3029d66949188bc149bf15ca9c709ec6ad105c68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3540360 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#983741} -- wpt-commits: fdae5a3dc97ed6f6570772bd5eebd8b3ff853213 wpt-pr: 33284
61ddeb2f8aa5308db794229cf33b5088d6db0c49: Bug 1760593 [wpt PR 33280] - A nested multicol fragment may be found inside a line., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 24 Mar 2022 12:10:21 +0000 - rev 687302
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760593 [wpt PR 33280] - A nested multicol fragment may be found inside a line., a=testonly Automatic update from web-platform-tests A nested multicol fragment may be found inside a line. If we have an inline formatting context with a floated multicol with an OOF inside, and the floated multicol is inside another fragmentation context, we failed to find and replace the fragment in the special OOF layout pass for block fragmentation. One does not (always) simply search inside child fragments of the containing block. Bug: 1307990 Change-Id: Icfe3e12d9de6c440a4010e6b7f7f99a6bbd3e5a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3540020 Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#983739} -- wpt-commits: 1280feb67a0050a2ad832ab73cb531cbd6332289 wpt-pr: 33280
7fb35b0768c2b97dcf5d56b1f1dac10f1375ccf6: Bug 1758526 [wpt PR 33113] - Use httpx for wptserve tests instead of hyper, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 24 Mar 2022 12:10:16 +0000 - rev 687301
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1758526 [wpt PR 33113] - Use httpx for wptserve tests instead of hyper, a=testonly Automatic update from web-platform-tests Use httpx for wptserve tests instead of hyper hyper is no longer maintained, and doesn't work with Python 3.10. The vendored hyper is removed entirely, and replaced by httpx installed using pip. Tests are updated, mostly in trivial ways. A few cases are interesting: - When httpx is used to POST, `handle_data` ends up called two times instead of once, first with the data, and then with an empty byte string. Whether this is an httpx bug or not, test_h2_data.py and test_h2_headers_data.py are adapted to deal with this, and changed to case-swap the input instead so that no buffering is needed. - `test_encode` previously failed an assert in the handler, but the response wasn't checked at all, so this wasn't noticed. - `test_push` is dropped since it can't be tested using httpx. - `test_raw_header_frame_invalid` is dropped since it ends up testing the error handling of the client, and httpx doesn't treat this input as an error. A better test would just check what bytes were sent over the wire, but don't bother, it's more work than seems justified. - `test_http_version` is added to make sure these tests keep using HTTP/2 even if httpx behavior changes in the future. Fixes https://github.com/web-platform-tests/wpt/issues/28784. Fixes https://github.com/web-platform-tests/wpt/issues/31315. -- wpt-commits: 05ae936451baacd34744c539ad34388617e12190 wpt-pr: 33113
ce29c5ce1c4ae1081bc309c437be6e29d8a31571: Bug 1760703 [wpt PR 33288] - Bump types-requests from 2.27.13 to 2.27.14 in /tools, a=testonly
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> - Thu, 24 Mar 2022 12:09:24 +0000 - rev 687300
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760703 [wpt PR 33288] - Bump types-requests from 2.27.13 to 2.27.14 in /tools, a=testonly Automatic update from web-platform-tests Bump types-requests from 2.27.13 to 2.27.14 in /tools Bumps [types-requests](https://github.com/python/typeshed) from 2.27.13 to 2.27.14. - [Release notes](https://github.com/python/typeshed/releases) - [Commits](https://github.com/python/typeshed/commits) --- updated-dependencies: - dependency-name: types-requests dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> -- wpt-commits: 7798f73544f98716e15b158fd3b204e437be5176 wpt-pr: 33288
1275d350ef031629fa8c35e13457cbb6cf63799c: Bug 1760738 [wpt PR 33295] - Remove subresource loading with WebBundles's WPT of <link>-based API, a=testonly
Hayato Ito <hayato@chromium.org> - Thu, 24 Mar 2022 12:09:19 +0000 - rev 687299
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760738 [wpt PR 33295] - Remove subresource loading with WebBundles's WPT of <link>-based API, a=testonly Automatic update from web-platform-tests Remove subresource loading with WebBundles's WPT of <link>-based API See bug 1306725 for details. As a first step, let's remove WPT tests of <link>-based API for which we have WPT of <script>-based API too. Note that link-*.html files which this CL doesn't remove yet are: - link-csp-allowed.https.tentative.html - link-csp-blocked.https.tentative.html - link-csp-blocked.https.tentative.html.sub.headers It is not immediately obvious that we can remove these. Let's remove or migrate these in a follow-up CL. A rough plan to remove <link>-based API is: 1. Remove all <link>-based API tests or migrate them to <script>-based API if required. 2. Refactor <script>-based API tests to remove abstraction layer, which is no longer necessary. 3. Drop the support of <link>-based API. Bug: 1306725 Change-Id: I91afe74c73c91cee922b10efe63c421c059629f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3539725 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/main@{#983672} -- wpt-commits: bedad4e725c420620195dd1961a8861c4fabe751 wpt-pr: 33295
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip