9e75d903108034bc94493f1309fda5f669778f86: Bug 1612706 [wpt PR 21539] - Add new comprehensive test for image-set rendering, a=testonly
Noam Rosenthal <noamr@users.noreply.github.com> - Mon, 17 Feb 2020 17:03:23 +0000 - rev 514490
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1612706 [wpt PR 21539] - Add new comprehensive test for image-set rendering, a=testonly Automatic update from web-platform-tests Add new comprehensive test for image-set rendering (#21539) * Add new comprehensive test for image-set rendering * Use dpr 1 for now for test - no sufficient infra for DPR setting -- wpt-commits: 1b7dcb06ea477226e90ca0fbc0b86262a410f7ad wpt-pr: 21539
ec7efef9ea874e5edf5fdb6f7c96ea5f7612de5f: Bug 1615951 [wpt PR 21828] - Remove CSS Rhythmic Sizing tests, a=testonly
Koji Ishii <kojii@chromium.org> - Mon, 17 Feb 2020 17:03:18 +0000 - rev 514489
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615951 [wpt PR 21828] - Remove CSS Rhythmic Sizing tests, a=testonly Automatic update from web-platform-tests Remove CSS Rhythmic Sizing tests Two years ago, when applying vertical rhythm algorithms, the risk of accidental rounding up was raised. This is a widely known, unavoidable risk in any vertical rhythm algorithms. The CSSWG was in favor to accept it 8 years ago, but this time, two members considered the risk is critical. https://github.com/w3c/csswg-drafts/issues/938 Last month, the CSSWG discussed this again. One invited expert was still strong not to accept the risk, and that the CSSWG resolved to remove tests. https://github.com/w3c/csswg-drafts/issues/938#issuecomment-577640685 Reduces 4 failures, as the feature is no longer implemented in LayoutNG nor in any other implementations. TBR=ikilpatrick@chromium.org, tabatkins@chromium.org Bug: 586413 Change-Id: Ia0d50d77550cc5c8b681f001a4f25a825e6504ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059692 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#741820} -- wpt-commits: ac16628eb7eb601957382053011363d2bcf8ce44 wpt-pr: 21828
7f1ee3df709eb0bc6695abcc16e58a1fdd36876c: Bug 1615869 [wpt PR 21820] - [LayoutNG] Generate first baseline for kInlineBlock baseline algorithm., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Mon, 17 Feb 2020 17:03:13 +0000 - rev 514488
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615869 [wpt PR 21820] - [LayoutNG] Generate first baseline for kInlineBlock baseline algorithm., a=testonly Automatic update from web-platform-tests [LayoutNG] Generate first baseline for kInlineBlock baseline algorithm. In https://chromium-review.googlesource.com/c/chromium/src/+/1988376 I simplified the logic a little too much. We (occasionally) need the first-baseline of a child inside an inline-block. We need this when we are aligning a list-marker. This modifies the NGBaselineAlgorithmType::kInlineBlock to always produce both the first and last baselines. Bug: 1051181 Change-Id: I4844dfe44d3525a68ee8b8d7f0f50bd995de9367 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057344 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#741798} -- wpt-commits: 2cd67814c72b152489684d47023a7a5ce9d0aced wpt-pr: 21820
2d343ee199327a05929787abde1d2fd5d603a088: Bug 1615754 [wpt PR 21811] - Update test processing of StageParameters changes, a=testonly
Alex Cooper <alcooper@chromium.org> - Mon, 17 Feb 2020 17:03:08 +0000 - rev 514487
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615754 [wpt PR 21811] - Update test processing of StageParameters changes, a=testonly Automatic update from web-platform-tests Update test processing of StageParameters changes Currently the test code only sends the stage parameters as Display Info updates. Now that WebVr has been removed, this code path is one that is being considered for removal. The real runtimes utilize both this VRDisplayInfo update path as well as updating the stage parameters with frame data. This changes the test runtime to do the same (i.e. send up stage parameters via both DisplayInfo and FrameData). Fixed: 983363 Change-Id: I3c0a3f59b97163c3ac3b8f4b6529183142688d0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056501 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Auto-Submit: Alexander Cooper <alcooper@chromium.org> Reviewed-by: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#741671} -- wpt-commits: 8debe68e88d3b10393ea3dc5862d4130c663f496 wpt-pr: 21811
2157de86143ff7a756926e7be0f5008f28e42ba9: Bug 1615440 [wpt PR 21788] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 16 Feb 2020 16:08:39 +0000 - rev 514486
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615440 [wpt PR 21788] - Update wpt metadata, a=testonly wpt-pr: 21788 wpt-type: metadata
5b625db071810b7539c8823c0396331d7f3f26bf: Bug 1615440 [wpt PR 21788] - [Image-Orientation] Fix canvas drawImage, a=testonly
Stephen Chenney <schenney@chromium.org> - Mon, 17 Feb 2020 17:03:00 +0000 - rev 514485
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615440 [wpt PR 21788] - [Image-Orientation] Fix canvas drawImage, a=testonly Automatic update from web-platform-tests [Image-Orientation] Fix canvas drawImage Image orientation was not correctly applied in base_rendering_context_2d, resulting in always oriented images sometimes drawn with the wrong source rect. This change fixes that. The image-orientation setting we respect always comes from the canvas into which the image is being drawn. This keeps the rules for which orientation to apply simple. As part of this change, orientation is added to StaticBitmapImage and used in the necessary cases to track the orientation of the source image. As part of this change, the code to correct an image source rect is moved to Image and callers updated. Bug: 1043790 Change-Id: I13d74b66cff912382f8f5efe0050eae6a0f283c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2044050 Reviewed-by: Fredrik Söderquist <fs@opera.com> Reviewed-by: Xida Chen <xidachen@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Fernando Serboncini <fserb@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Auto-Submit: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#741635} -- wpt-commits: 24baba70548b528ff0179b22c77ddaabb8134a7d wpt-pr: 21788
bff06fdf41233656d3f9f3e8f8bb720dc40e606c: Bug 1615803 [wpt PR 21819] - Fix lint.whitelist after 8636d91, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Mon, 17 Feb 2020 17:02:55 +0000 - rev 514484
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615803 [wpt PR 21819] - Fix lint.whitelist after 8636d91, a=testonly Automatic update from web-platform-tests Fix lint.whitelist after 8636d91 (#21819) The lint for audit.js is based on the exact line location, which changed when https://github.com/web-platform-tests/wpt/pull/21804 added two more lines to the file. -- wpt-commits: 089627b582021a156250007160690ee7d339c0ea wpt-pr: 21819
be8d9c0c689d628c9c637f909c039fdff7f0e98e: Bug 1598797 [wpt PR 20414] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 17 Feb 2020 15:15:02 +0000 - rev 514483
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1598797 [wpt PR 20414] - Update wpt metadata, a=testonly wpt-pr: 20414 wpt-type: metadata
50803bf833e145f8aa2fc54dda48e5210dade900: Bug 1598797 [wpt PR 20414] - Adds flex gap tests, a=testonly
Adam Argyle <argyle@google.com> - Mon, 17 Feb 2020 17:02:47 +0000 - rev 514482
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1598797 [wpt PR 20414] - Adds flex gap tests, a=testonly Automatic update from web-platform-tests Adds flex gap tests (#20414) * horizontal test stubbed * vertical test stubbed * adding basic horizontal gap test * adding basic vertical flex gap test * adding flex wrap gap test on extrinsic children * adding horizontal flex gap test on intrinsic children * adding vertical flex gap test on intrinsic children * cruft removal * adding horizontal flex gap test on wrapping intrinsic children * adding vertical flex gap test on wrapping intrinsic children * started writing mode gap tests * page title fixes and switched to logical sizing * flex vertical stack writing mode tests and refs done * renamed file to be more succinct * rtl tests for flex stacks * removed gaps from ref impls * title updates * renamed files to scale better with the test matrix * rows and columns writing mode tests are good * intrinsic columns writing mode tests are good * intrinsic rows writing mode tests are good * wrap intrinsic writing mode tests are good * wrap intrinsic columns writing mode tests are good * test for separative row and column gap sizes * update match meta to latest ref test title * mixed units gaps, percentage and rem * calc flex gap examples * cruft fix * fix human assertion text * pacify linter * fixes colors, updates copy -- wpt-commits: 8037fe7f0d98f045bc813f3e21f228a2821dca5e wpt-pr: 20414
ade48427aa143e7b17cc5697d30f0caad064bb9d: Bug 1615638 [wpt PR 21804] - Link to github issue explaining why webaudio's audit.js exists, a=testonly
Luke Zielinski <44509484+LukeZielinski@users.noreply.github.com> - Mon, 17 Feb 2020 17:02:40 +0000 - rev 514481
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615638 [wpt PR 21804] - Link to github issue explaining why webaudio's audit.js exists, a=testonly Automatic update from web-platform-tests Link to github issue explaining why webaudio's audit.js exists (#21804) -- wpt-commits: 8636d919cb3584807955d30ef2c1024cf74e29cc wpt-pr: 21804
f96adf658c0022e7d49ff183d8ea585e3ec7b787: Bug 1594165 [wpt PR 20096] - [LayoutNG] Text indent with leading float, a=testonly
Alison Maher <almaher@microsoft.com> - Mon, 17 Feb 2020 17:02:35 +0000 - rev 514480
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1594165 [wpt PR 20096] - [LayoutNG] Text indent with leading float, a=testonly Automatic update from web-platform-tests [LayoutNG] Text indent with leading float This change avoids breaking after leading floats in the case where there is a text indentation. Doing so fixes the following scenario: <div style="width: 100px; text-indent: 40px;"> <div style="float: left; width: 60px; height: 10px;"></div> <div style="display: inline-block; width: 60px; height: 20px;"></div> </div> In the above example, the following steps will happen: 1. The inline div will attempt to fit on the same line as the float. It does not, and a new line opportunity will be created on the next line. 2. The inline div overflows this new line opportunity due to the indent. 3. HandleOverflow() checks if the previous element (ie. the float) can break after. The float can, so it will attempt to rewind. 4. This causes a break in a later DCHECK. Not allowing breaks after leading floats in the case of an indentation fixes the above issue, and appears to match the behavior of other browsers. Bug: 1014247 Change-Id: Icf551f5908a0fcb8e0b80a8b9329c965435dd805 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1896509 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#741487} -- wpt-commits: 3c631e2f32dae04804e5cc0f1448cf5e8615458b wpt-pr: 20096
caf35304b609108af7b3ae90ca5472ee8ccfc0df: Bug 1612419 [wpt PR 21518] - getAnimations from the Document instead of from Timeline, a=testonly
haozhe <haozhes@chromium.org> - Mon, 17 Feb 2020 17:02:30 +0000 - rev 514479
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1612419 [wpt PR 21518] - getAnimations from the Document instead of from Timeline, a=testonly Automatic update from web-platform-tests getAnimations from the Document instead of from Timeline Per the spec, Document::getAnimations() must report all Animations whose target effect is the given document. Spec: https://drafts.csswg.org/web-animations/#extensions-to-the-documentorshadowroot-interface-mixin Bug: 828585 Change-Id: I92a5cab69d0b9869fea0238e2cfb8e98d995a3b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024539 Commit-Queue: Hao Sheng <haozhes@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#741473} -- wpt-commits: e617314c6aa4b7c0fb83627d47063d00106b47a1 wpt-pr: 21518
86aea38a333721944a11ba003451431877c87c80: Bug 1614081 [wpt PR 21675] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Feb 2020 17:00:32 +0000 - rev 514478
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1614081 [wpt PR 21675] - Update wpt metadata, a=testonly wpt-pr: 21675 wpt-type: metadata
65570736bd96a5c315edcba85e114f29cd5d7f4e: Bug 1614081 [wpt PR 21675] - [css-scroll-anchoring] Add WPT for zero scroll offset suppression., a=testonly
Nick Burris <nburris@chromium.org> - Mon, 17 Feb 2020 17:02:22 +0000 - rev 514477
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1614081 [wpt PR 21675] - [css-scroll-anchoring] Add WPT for zero scroll offset suppression., a=testonly Automatic update from web-platform-tests [css-scroll-anchoring] Add WPT for zero scroll offset suppression. Chromium has always had a scroll anchoring suppression trigger when the scroll offset is zero. This suppression trigger was added to the spec in https://github.com/w3c/csswg-drafts/pull/4679. Change-Id: I2f38b23803e610aa04976c43211357e173cecbb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2045200 Commit-Queue: Nick Burris <nburris@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#741108} -- wpt-commits: 91d1d5d10ddb68fcee2c1c66f27f53b7bd50001f wpt-pr: 21675
ec2e37b3e9188a10c7aa650195da6a7024da057d: Bug 1615048 [wpt PR 21763] - Update chromium logger to identify subtest failures., a=testonly
Luke Zielinski <44509484+LukeZielinski@users.noreply.github.com> - Mon, 17 Feb 2020 17:02:16 +0000 - rev 514476
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615048 [wpt PR 21763] - Update chromium logger to identify subtest failures., a=testonly Automatic update from web-platform-tests Update chromium logger to identify subtest failures. (#21763) This also fixes a bug where a subtest failure would be hidden because the expected_status was evaluated too late in `test_end`. For a subtest failurei the test status is Pass. But for Chromium, we flip this "actual" status to a failure. But the actual status is also used as a fall-back for the expected status (see explanation in chromium.py:126). So if "expected" is evaluated after the "flip", it will just match "actual" and the failure will be marked as an "expected" failure. -- wpt-commits: 22a79941ccc023ef301a48734158451f1b8873fb wpt-pr: 21763
beddcdb8063fb6a9d54501667e87d47b5529277d: Bug 1615484 [wpt PR 21793] - Update interfaces/web-bluetooth.idl, a=testonly
autofoolip <auto@foolip.org> - Mon, 17 Feb 2020 17:02:11 +0000 - rev 514475
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615484 [wpt PR 21793] - Update interfaces/web-bluetooth.idl, a=testonly Automatic update from web-platform-tests Update interfaces/web-bluetooth.idl (#21793) Source: https://github.com/tidoust/reffy-reports/blob/2b78fd5/ed/idl/web-bluetooth.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/650224276 -- wpt-commits: cebcce0e9b4c105a3ddb40383d7b5cdb7adefd03 wpt-pr: 21793
1882083938fbd63bb41b94788e4e604c41c709e3: Bug 1615605 [wpt PR 21802] - Use errno attribute to handle socket.error for PY2 and PY3 compatibility, a=testonly
Ziran Sun <zsun@igalia.com> - Mon, 17 Feb 2020 17:02:06 +0000 - rev 514474
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615605 [wpt PR 21802] - Use errno attribute to handle socket.error for PY2 and PY3 compatibility, a=testonly Automatic update from web-platform-tests Use errno attribute to handle socket.error for PY2 and PY3 compatibility Python 3 has introduced Built-in Exception class 'ConnectionRefusedError' as a subclass of ConnectionError for connection-related issue. -- wpt-commits: f2682272ecf2883db0f5302d8fae6d1b74411d64 wpt-pr: 21802
b58314ba724365c522877e66c76b9b00c32f1a52: Bug 1615410 [wpt PR 21787] - Update docs around wpt-pr-bot, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Mon, 17 Feb 2020 17:02:01 +0000 - rev 514473
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615410 [wpt PR 21787] - Update docs around wpt-pr-bot, a=testonly Automatic update from web-platform-tests Update docs around wpt-pr-bot Closes https://github.com/web-platform-tests/wpt/issues/21752 -- wpt-commits: b090f21d2d9a3870b8d13d37070ccdb380a85f46 wpt-pr: 21787
cbe2cf51c32904b410d25b01f6cb5ffc48a81d8e: Bug 1615593 [wpt PR 21801] - Revert "Worker: Add data URL tests for nested dedicated workers", a=testonly
Stephen McGruer <smcgruer@chromium.org> - Mon, 17 Feb 2020 17:01:56 +0000 - rev 514472
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615593 [wpt PR 21801] - Revert "Worker: Add data URL tests for nested dedicated workers", a=testonly Automatic update from web-platform-tests Revert "Worker: Add data URL tests for nested dedicated workers" This reverts commit 1d73a2eb29cb7088b4920cf8958b6b3d053b093a. Reason for revert: Worker variant of tests appears to consistently timeout on WebKit Linux Leak (crbug.com/1052322) Original change's description: > Worker: Add data URL tests for nested dedicated workers > > This CL renames data-url.html to data-url.any.js in order to run the > tests on a dedicated worker. Previously these tests only ran on window. > > Bug: n/a > Change-Id: I4be0cfdddc01fa4865763868c4947ea63e62d491 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2054656 > Reviewed-by: Makoto Shimazu <shimazu@chromium.org> > Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> > Cr-Commit-Position: refs/heads/master@{#741367} TBR=nhiroki@chromium.org,shimazu@chromium.org Change-Id: I00481f9a51c672b4041364674d0bcad00d959c63 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: n/a Bug: 1052322 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057046 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#741417} -- wpt-commits: a36ca8f94aed6644abaab1553dd634f3f5251a5d wpt-pr: 21801
f46cad72fb729d24e6d7a006e8f208ff69adcd7b: Bug 1615542 [wpt PR 21798] - [Layout] SetNeedsLayout when an flex-item image loads, a=testonly
David Grogan <dgrogan@chromium.org> - Mon, 17 Feb 2020 17:01:51 +0000 - rev 514471
Push 37136 by opoprus@mozilla.com at Wed, 19 Feb 2020 04:34:03 +0000
Bug 1615542 [wpt PR 21798] - [Layout] SetNeedsLayout when an flex-item image loads, a=testonly Automatic update from web-platform-tests [Layout] SetNeedsLayout when an flex-item image loads Reland of https://chromium-review.googlesource.com/c/chromium/src/+/2055794 . Looks like external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/flexbox/flexbox-intrinsic-ratio-003v.html wasn't fixed by this. Change-Id: I14c34662b6750a528e6b60a01ba68b58e419f359 Bug: 1052029, 1042329 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055794 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#741392} -- wpt-commits: ddba88c0796691e1b6b94f2dea159040959933cb wpt-pr: 21798
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip