Automatic update from web-platform-tests
Add reporting.idl as a dep for CSP idlharness.js tests (#15864)
Needed for https://github.com/web-platform-tests/wpt/pull/15856.
--
wpt-commits: d779352beb7f08f4970ab1512c8e5ac9ff8cded6
wpt-pr: 15864
Automatic update from web-platform-tests
Use step_timeout() to force spin the EventLoop (#16142)
Use step_timeout() to force spin the EventLoop. Also allow eventPromise to reject before acceptPromise resolves.
--
wpt-commits: 3bfdeb8976fc51748935c8d1f1014dfba8e08dfb
wpt-pr: 16142
Automatic update from web-platform-tests
HTML: named objects of navigated documents
For https://github.com/whatwg/html/pull/4404.
--
wpt-commits: 52bd6d9692ccd589c089d89bf59142cfc0e98288
wpt-pr: 15769
Automatic update from web-platform-tests
[visual viewport] Wait for all tests to be defined
Configure the test harness to delay completion until all
asynchronously-defined tests are available.
--
wpt-commits: c6b4c117ceb0f89201188d017d6ba4b1e6cf1262
wpt-pr: 15633
Automatic update from web-platform-tests
[css-tables] Test for height distribution after modifying layout tree
I don't foresee us fixing this until NG.
This is a test only, no behavior change.
Bug: 764031
Change-Id: I9afddd0bf09231d2f0981e75eb70e7ba1828ee58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1542305
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#645344}
--
wpt-commits: 4d956906ca1d5799369c468dde7888eb0b2e5ffb
wpt-pr: 16120
Automatic update from web-platform-tests
Extend canvas getContextAttributes WPTest
This CL extend the WPTest for Canvas getContextAttributes to include
the |desynchronized|.
This CL covers the flag WPT test extension mentioned in
https://github.com/whatwg/html/pull/4360 (which addressed
https://github.com/whatwg/html/issues/4087).
Bug: 944199, 945835
Change-Id: Ibb339c66014d7579023f75c7f2cef99e3f03d351
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538491
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644332}
--
wpt-commits: c3f8e5c0bb15e7d7f57dbe60f6869caa0c4ad2e7
wpt-pr: 16084
Automatic update from web-platform-tests
[ElementTiming] Mimic FCP++ rect computations
This CL changes ElementTiming rect computation to use a computation
similar to that used by FCP++, but relative to the owning frame.
The tests show that the new computation seems more accurate as they
uncovered a problem with the SVG test: default SVG size is 300x150 so
it was clipping the <image> element inside.
A test for rect coordinates relative to iframe is added.
Bug: 879270, 943138
Change-Id: Ib8fa266bda76843fbf7ca07f82ac5bb245d52c4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531503
Reviewed-by: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#645021}
--
wpt-commits: 5570bb27d55420f0639dab2415e618afdb94a6f6
wpt-pr: 15936
Automatic update from web-platform-tests
[Azure Pipelines] Run daily run of Safari stable (#16108)
Rather than adding support for getting the version of Safari stable using
PlistBuddy in tools/wpt/browser.py, pass in the version with
`--browser-version` and make sure that it is not overwritten internally.
The next stable Safari release should support `safaridriver --version`.
--
wpt-commits: 146c7368173ea5336d39049788d993f93774eca6
wpt-pr: 16108
Automatic update from web-platform-tests
Catch more exceptions in Document-createElement-namespace (#16099)
--
wpt-commits: 8f8cbc5ce2a728ad2b48f58085977b8793c95f2b
wpt-pr: 16099
Automatic update from web-platform-tests
Adding WPT for accepting an offer to receive simulcast.
This test checks that when a PeerConnection receives an offer from
an SFU indicating that the SFU wants to receive simulcast, it generates
an answer that negotiates sending simulcast.
Bug: None
Change-Id: I1b6623169a1c2fd18ee453bfbf8e63cee95e5bd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540306
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Amit Hilbuch <amithi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644886}
--
wpt-commits: c2bd80a32f478b4029307523d6ee02c2aa695b19
wpt-pr: 16092
Automatic update from web-platform-tests
[Azure Pipelines] Skip checkout for wpt.fyi hook jobs (#16112)
No checkout is needed. This will save ~40s, which for PRs could matter.
--
wpt-commits: 1815dd1f3ffb0ea81ab5ae43a2335d930cd31689
wpt-pr: 16112
Automatic update from web-platform-tests
Add experimental :picture-in-picture CSS pseudo-class
This CL adds support for an experimental CSS pseudo-class used to detect
when an element enters and leave Picture-in-Picture.
Spec: https://github.com/WICG/picture-in-picture/pull/120
Intent to Implement & Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/X-qPSmdSR_g
Bug: 940404
Change-Id: Id225eaff841f7338927d5e150ba9ad6b97dcb258
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1511459
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644853}
--
wpt-commits: d0396cc595c60b71d52092dc640a956b76051a9f
wpt-pr: 15743
Automatic update from web-platform-tests
[ElementTiming] Add carousel image test
This CL adds a test for carousel images. The test contains a carousel of
two images which has a timeout to change image every 50 ms. Because the
images are completely removed from the page and then readded, Element
Timing detects the new addition as a new element, so a new entry is
dispatched every time. This is helpful for measuring latency, for
example when the image carousel change is prompted by user input.
Bug: 879270
Change-Id: I84a034d307c026ba50d12d8bb6241a7fceeadae5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540457
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644834}
--
wpt-commits: 43dda2a1b3632c91c247bb00bd617847213a9c9c
wpt-pr: 16100
Automatic update from web-platform-tests
Allow run-all jobs to run on non-master branches
--
wpt-commits: 2cfcea72fb19c0065fffacb182cdf8709d241e3c
wpt-pr: 16117
Automatic update from web-platform-tests
Change unoptimized-images feature policy to unoptimized-lossy-images.
This makes it more clear that this policy applies only to lossy image
types (for now, just JPEG). This patch also makes the implementation
more generic in order to make the policy compatible with parsed
policy values and to pave the way for implementing a
lossless-enforcing version of the unoptimized-images policy as well.
This is a reland of this reverted CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1531354
Bug: 942659
Change-Id: I7928de8a7f3e66841ec3792a4152a3570a709ca3
TBR: iclelland@chromium.org,pdr@chromium.org,kenrb@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1541579
Commit-Queue: Paul Meyer <paulmeyer@chromium.org>
Reviewed-by: Paul Meyer <paulmeyer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644832}
--
wpt-commits: 1d5e060c91fdb8bf66d9246fc1d19b53c89a33ba
wpt-pr: 16115
Automatic update from web-platform-tests
Revert "Fix external/wpt/event-timing/event-timing-onloadobserve.html to be more deterministic"
This reverts commit 250c950a568a7614d72b4fa319d86cf2d9b46cf0.
Reason for revert: Timing out on all bots: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=external/wpt/event-timing/event-timing-onloadthenobserve.html&testType=webkit_layout_tests
Original change's description:
> Fix external/wpt/event-timing/event-timing-onloadobserve.html to be more deterministic
>
> This test passes as some events like click or mousedown for the first
> click are missed at the second PerformanceObserver in startObserver.
> This CL makes sure that the first PerformanceObserver does not proceed
> until the first click event happens.
>
> Actually we found the test failed when we use a different task runner is
> used for WidgetInputHandler (https://chromium-review.googlesource.com/c/chromium/src/+/1530492/4).
>
> Bug: 872081
> Change-Id: I8d8fe187b8053140f40ae9cf08737fcf7b64233c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538136
> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
> Reviewed-by: Alexander Timin <altimin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#644321}
TBR=hajimehoshi@chromium.org,altimin@chromium.org,npm@chromium.org
Change-Id: Ibb4e463906f5b8040e96c7e008e999c638630e79
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 872081
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540085
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644443}
--
wpt-commits: 65cfcd3c4f5d3d16bc38e1f34dd5bce3fe3402de
wpt-pr: 16090
Automatic update from web-platform-tests
Revert "Change unoptimized-images feature policy to unoptimized-lossy-images."
This reverts commit efbe41b8ceda53be0e82b4c9a4576cc95c84a3b5.
Reason for revert: Mac bots are failing consistently, see e.g. https://ci.chromium.org/p/chromium/builders/ci/Mac10.10%20Tests/40949
Original change's description:
> Change unoptimized-images feature policy to unoptimized-lossy-images.
>
> This makes it more clear that this policy applies only to lossy image
> types (for now, just JPEG). This patch also makes the implementation
> more generic in order to make the policy compatible with parsed
> policy values and to pave the way for implementing a
> lossless-enforcing version of the unoptimized-images policy as well.
>
> These changes have been pulled from a larger partially reviewed CL:
> https://chromium-review.googlesource.com/c/chromium/src/+/1524869
>
> Bug: 942659
> Change-Id: I0242ac900b1653b89d6d8dbd63616003dcaaba62
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531354
> Commit-Queue: Paul Meyer <paulmeyer@chromium.org>
> Reviewed-by: Paul Meyer <paulmeyer@chromium.org>
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Reviewed-by: Ken Buchanan <kenrb@chromium.org>
> Reviewed-by: Ian Clelland <iclelland@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#644488}
TBR=flackr@chromium.org,kenrb@chromium.org,pdr@chromium.org,paulmeyer@chromium.org,iclelland@chromium.org
Change-Id: I0dc0449dc2d07c5dafa84c7123ec664c902a73fb
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 942659
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540145
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644637}
--
wpt-commits: ef78bcb3870680baf3b2f965def061b5858ac88c
wpt-pr: 16114
Automatic update from web-platform-tests
Change unoptimized-images feature policy to unoptimized-lossy-images.
This makes it more clear that this policy applies only to lossy image
types (for now, just JPEG). This patch also makes the implementation
more generic in order to make the policy compatible with parsed
policy values and to pave the way for implementing a
lossless-enforcing version of the unoptimized-images policy as well.
These changes have been pulled from a larger partially reviewed CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1524869
Bug: 942659
Change-Id: I0242ac900b1653b89d6d8dbd63616003dcaaba62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531354
Commit-Queue: Paul Meyer <paulmeyer@chromium.org>
Reviewed-by: Paul Meyer <paulmeyer@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644488}
--
wpt-commits: f19a0c4003dc469cd0972dab425acdcdd3a7d1d7
wpt-pr: 16113
Automatic update from web-platform-tests
Don't use HEAD or FETCH_HEAD to checkout specific revisions. (#16066)
FETCH_HEAD is unreliable because it's a global variable that can be
accidentially clobbered by adding an additional fetch anywhere in the
pipeline. As a result running tests in CI has been broken since we
chose the wrong revisions. HEAD is more reliable but doesn't exist
until we first check something out.
Instead, do the following:
* Fetch the initial commits into a branch called task_head and check
this out unconditionally.
* For PRs, create branches called base_head and pr_head pointing to
the two parents of the merge commit that we test on PRs.
* Express all the other revisions in terms of task_head, pr_head and
base_head, since they are both correct and more descriptive than
using complex revision specifiers.
* Move as much logic as possible out of the script baked in to the
docker image since that's hardest to update.
--
wpt-commits: e5044ace1ad217e683fb239ce6f88806f05139e3
wpt-pr: 16110
Automatic update from web-platform-tests
Implement `Sec-Fetch-Site: 'none'` for user-initiated navigations.
https://mikewest.github.io/sec-metadata/#sec-fetch-site-header defines
a `none` value for `Sec-Fetch-Site`, which should be delivered along with
navigational requests which were initiated directly from the browser, and
not from a user's interaction with websites.
This patch implements this new value in
`NavigationRequest::AddAdditionalRequestHeaders`, and adds tests for some
of the core use cases we expect servers to care about when examining
this header: address bar navigations, and bookmark navigations.
We'll add additional test cases in future patches as we work out the right
answers to the questions raised in [1] and [2].
[1]: https://mikewest.github.io/sec-metadata/#directly-user-initiated
[2]: https://docs.google.com/document/d/1YdakWfCR29pVNHURgceKrM_zjGN61xdnCXdZIGpQzxQ
Bug: 868286
Change-Id: I4866daba27a8763966cf3b213d0c0e916c0db787
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1520667
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644760}
--
wpt-commits: 696d3a7aebc3c610eeddee94fb490aa6662c7e79
wpt-pr: 15806
Automatic update from web-platform-tests
Remove orphan Travis files (#16087)
Remove some shell scripts that were used on Travis and are no longer needed
--
wpt-commits: 37db772678555b4bad7bf215158d3750d56a6ae2
wpt-pr: 16087
Automatic update from web-platform-tests
Run full Edge runs every 6 hours (#16107)
This will end up in the same build as the Safari TP run. The wpt.fyi
integration should ensure that one failing doesn't affect the other,
but there is some risk here and it will need to be monitored.
--
wpt-commits: b53840ae8e05244f694a32d411251c009c249a26
wpt-pr: 16107
Automatic update from web-platform-tests
[wptrunner] Remove unused requirements (#16102)
* [wptrunner] Remove unnecessary Chrome dependency
The Chrome "browser" abstraction has not required the `selenium` package
since it was refactored to use WebDriver [1]. Update the corresponding
pip requirements file accordingly.
[1] caf4aa367efef641c4b0e5dfd1c8970eb102f060
* [wptrunner] Remove unnecessary Safari dependency
The Safari "browser" abstraction has not required the `selenium` package
since it was refactored to use WebDriver [1]. Update the corresponding
pip requirements file accordingly.
[1] f13770f6053eb26328adf487c7f80431da5c4509
--
wpt-commits: a0e57a6548891b912ee804b9d4ff289efb0dd7e4
wpt-pr: 16102
Automatic update from web-platform-tests
[js] Remove invalid tests for JavaScript built-ins
The 2015 edition of ECMAScript modified the semantics of a number of
built-in methods to tolerate non-object values [1]. The tests asserting
a TypeError under these conditions are no longer valid.
[1] https://tc39.github.io/ecma262/#sec-additions-and-changes-that-introduce-incompatibilities-with-prior-editions
--
wpt-commits: 32450b4dd65f4a69ba91df20581215a0d81c1daf
wpt-pr: 15333
Automatic update from web-platform-tests
Revert "Don't use HEAD or FETCH_HEAD to checkout specific revisions. (#16066)" (#16101)
This reverts commit 856a95f08c3674cf34edbd15cf51d4fbffe84a5c.
--
wpt-commits: fbd91b73ea03f23fffe4717556c088ae344c9501
wpt-pr: 16101
Automatic update from web-platform-tests
Part 0: Remove a bug from a meta file, and test that we aren't comparing offers with answers.
Differential Revision: https://phabricator.services.mozilla.com/D24096
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1531122
gecko-commit: ecb3fee216580948044845803338c60e3a283ffe
gecko-integration-branch: central
gecko-reviewers: jib
--
wpt-commits: 65f12c6cb3d58c8000400b76b9ab7f32961793e9
wpt-pr: 16039
Automatic update from web-platform-tests
Don't use HEAD or FETCH_HEAD to checkout specific revisions. (#16066)
FETCH_HEAD is unreliable because it's a global variable that can be
accidentially clobbered by adding an additional fetch anywhere in the
pipeline. As a result running tests in CI has been broken since we
chose the wrong revisions. HEAD is more reliable but doesn't exist
until we first check something out.
Instead, do the following:
* Fetch the initial commits into a branch called task_head and check
this out unconditionally.
* For PRs, create branches called base_head and pr_head pointing to
the two parents of the merge commit that we test on PRs.
* Express all the other revisions in terms of task_head, pr_head and
base_head, since they are both correct and more descriptive than
using complex revision specifiers.
* Move as much logic as possible out of the script baked in to the
docker image since that's hardest to update.
--
wpt-commits: 856a95f08c3674cf34edbd15cf51d4fbffe84a5c
wpt-pr: 16066
Automatic update from web-platform-tests
Upload MANIFEST.json.bz2 and MANIFEST.json.zst (#16083)
The first half of #16081.
zstandard has the best compression ratio and fast decoding. bzip2 has good compression
and very slow decoding. gzip has poor compression and fast decoding. Overall zstandard
is alway the best to download + decompress, but relies on a third party Python package.
gzip is always the worst unless network is very fast and CPU very slow. So in the future
we will move to zstandard where possible and bzip2 where not possible.
--
wpt-commits: d5921ca1198a8f3ddbecd8392c1dada9c4aa8fbc
wpt-pr: 16083
Automatic update from web-platform-tests
Fix external/wpt/event-timing/event-timing-onloadobserve.html to be more deterministic
This test passes as some events like click or mousedown for the first
click are missed at the second PerformanceObserver in startObserver.
This CL makes sure that the first PerformanceObserver does not proceed
until the first click event happens.
Actually we found the test failed when we use a different task runner is
used for WidgetInputHandler (https://chromium-review.googlesource.com/c/chromium/src/+/1530492/4).
Bug: 872081
Change-Id: I8d8fe187b8053140f40ae9cf08737fcf7b64233c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538136
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644321}
--
wpt-commits: b3689e4125b4bde0e6f90d9144726ad4689ddd6d
wpt-pr: 16051
Automatic update from web-platform-tests
[LayoutNG] Ignore cached min/max widths tainted by extrinsics.
Some properties (e.g. percentage padding) cause the cached min/max
preferred inline sizes to be affected by the extrinsic size calculation.
We store preferred min/max *border box* sizes. When a shrink-to-fit
container has percentage-based inline padding, the resolved percentage
padding is part of the preferred size. So, what we store is no longer
purely intrinsic in this case, since percentages are resolved against
something on the outside. The values need to be updated if the size of
the containing block changes. Therefore, never re-use a previously
calculated min/max preferred inline size in such cases.
Remove code from NGBlockNode::Layout() which attempted to cope with such
situations by using the legacy layout engine to recalculate min/max
values. This doesn't work, because the legacy layout engine hasn't been
updated with the new containing block size at this point (which are
needed in order to resolve percentages correctly).
Bug: 932979
Change-Id: I884bb2777babe9dae785055bac5029d7ea941a66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538085
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644319}
--
wpt-commits: c3be5b409630ad5d6c82f22e24216383dcb53426
wpt-pr: 16079
Automatic update from web-platform-tests
Remove the build_css_testsuite job
This is no longer required. It's also the final job that uses travis
for anything.
--
wpt-commits: 87f87e1276cdbf9f4af14dcb12d3d7bc1200d7c5
wpt-pr: 16086
autofoolip
Philip Jägenstedt
Max Morin
Ian Clelland
Danyao Wang
Anne van Kesteren
Mike Pennisi
David Grogan
Mounir Lamouri
moz-wptsync-bot
Kunihiko Sakamoto
Miguel Casas-Sanchez
Nicolás Peña Moreno
Domenic Denicola
Ian Kilpatrick
Amit Hilbuch
François Beaufort
James Graham
Paul Meyer
Peter Kasting
Mike West
Koji Ishii
Sam Sneddon
Byron Campen [:bwc]
Philipp Hancke
Hajime Hoshi
Morten Stenshorne