Automatic update from web-platform-tests
Use gPV/sP, as that's slightly more well-supported
Requested by @emilio in <https://github.com/w3c/csswg-drafts/issues/3588#issuecomment-460019494>
--
Merge pull request #15286 from web-platform-tests/tabatkins-patch-1
Use gPV/sP, as that's slightly more well-supported
--
wpt-commits: f912ea28e7a5451f51d38d62cd0aee489618e4cb, ead8f8b00d0b68237109f3c93d0ccae076a34f98
wpt-pr: 15286
Automatic update from web-platform-tests
[Payment Request][WPT] Fix show() tests. (#15285)
Before this patch, the WPT tests for PaymentRequest.show() failed (and
were expected to do so) because the tests run in a content shell, which
does not have the Payment Request components sufficient for showing a
browser payment sheet.
This patch converts the show() test into a manual one, which should be
run in a full browser. One test case remains automated, because its
intent is to invoke show() without a user gesture. That test case is
expected to fail because Chromium does not require a user gesture for
show() at this time (https://crbug.com/817807).
After this patch, the manual WPT tests for PaymentRequest.show() pass in
the full Chromium browser.
Bug: 929773 817807
Change-Id: I9cacb5447fb3ae43a8b50c53a74b7c58db8f4466
--
wpt-commits: 9cd1c2970839f44d1d2fb0f6e862d4b05a1065ce
wpt-pr: 15285
Automatic update from web-platform-tests
[Payment Request][WPT] Fix abort() tests. (#15283)
Before this patch, the WPT tests for PaymentRequest.abort() were
expected to fail due to including the vendor testdriver JavaScript file
before the generic testdriver file. The vendor file was attempting to
use the objects defined in the generic file, but the incorrect include
order caused a JS error.
This patch reorders the vendor JS file to be after the generic JS file
and splits out the manual tests that require a user gesture for
PaymentRequest.show().
After this patch, the PaymentRequest.abort() tests are passing.
Bug: 929773
Change-Id: Ic0f8ff84b478116821e98775d1cec31cfad32d9f
--
wpt-commits: ba78e657cbc2648e1540216e5a7973bc91f221f0
wpt-pr: 15283
Automatic update from web-platform-tests
Do not require user gesture if pictureInPictureElement is set
Following https://github.com/WICG/picture-in-picture/issues/116, it
would be great to allow video to enter Picture-in-Picture without user
activation if there's already a visible PiP window in the context of the
document, in other words if `document.pictureInPictureElement` is set.
Bug: 928697
Change-Id: I2c191368d8dd1bd6ddade719399d0679ef410575
Reviewed-on: https://chromium-review.googlesource.com/c/1454360
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630026}
--
wpt-commits: 5692bc8fe5e5ae3703dda9f0689e1d8ec3431411
wpt-pr: 15247
Automatic update from web-platform-tests
[ElementTiming] Use TimingAllowOrigin check and remove bubbling
This CL changes the security check for ElementTiming from same-origin to
TAO, which requires plumbing the OriginalTimingAllowOrigin attribute for
the case of 304 responses. It also removes bubbling to be consistent with
ResourceTiming. Some tests are fixed to properly use cross-origins within
external/wpt, and a cross-origin resource with TAO wildcard test is
added. More TAO tests will be added in a followup.
Bug: 928425, 879270
Change-Id: I4df40818823e3db9851fbc9586a0bda9c1adcfec
Reviewed-on: https://chromium-review.googlesource.com/c/1453074
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630019}
--
wpt-commits: dcc3641354ccfcf7834bc80c28bf7890b9a8620d
wpt-pr: 15245
Automatic update from web-platform-tests
Stop running coverage by default in tox (#15278)
This doesn't re-enable it on CI because of #8613.
--
wpt-commits: 313a26544dbd0f99ee1a7618eae3bee494ab2ad2
wpt-pr: 15278
Automatic update from web-platform-tests
Revert "Link element events should be able to fire more than once"
This reverts commit 66236c640db16d71a5cd3f3e59638fb323d5f542.
Reason for revert: Bad and unexpected performance regressions were
introduced with this change. It is possible to incur an infinite loop
of loading a <link> and firing the load event, if the onload function
tampers with the `rel` attribute, as is sometimes done with preload links.
This may prevent a window's load event from ever being fired. Mitigating
problems like this needs to more looking into before this change can land
apparently.
Performance regression bugs: https://crbug.com/927427, https://crbug.com/928796, https://crbug.com/929153, https://crbug.com/929265. The original bug (https://crbug.com/922618) has been re-opened to track future work for this.
Original change's description:
> Link element events should be able to fire more than once
>
> As per spec https://html.spec.whatwg.org/multipage/links.html#link-type-stylesheet,
> the <link> element can have its load and error events fire multiple times,
> per resource it loads.
>
> Bug: 922618
> Change-Id: Ifc9ade076e119d5cf9f4eaf656c6ea7c1deb0ba9
> Reviewed-on: https://chromium-review.googlesource.com/c/1423601
> Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
> Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
> Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
> Cr-Commit-Position: refs/heads/master@{#628010}
TBR=yhirano@chromium.org,kouhei@chromium.org,domfarolino@gmail.com
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 922618
Change-Id: I0affe5a242bf472743d11a4905a630da7895cfca
Reviewed-on: https://chromium-review.googlesource.com/c/1457745
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Dominic Farolino <domfarolino@gmail.com>
Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
Cr-Commit-Position: refs/heads/master@{#629956}
--
wpt-commits: 56f29c8b1fb483069ceb4d4376ed369bb9543c1d
wpt-pr: 15273
Automatic update from web-platform-tests
XMLSerializer: Fix conflict between a generated ns* prefix and existing xmlns:ns*.
This CL restores the loop removed in crrev.com/629490.
The new behavior matches to Firefox though it doesn't conform to the
specification.
Add a test case to WPT based on the current specification, and
Blink has a failing expectation.
Bug: 928639
Change-Id: Ica431543440b538400cf1af086cab27cf59c4dc8
Reviewed-on: https://chromium-review.googlesource.com/c/1454023
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629842}
--
wpt-commits: c815526cd9d6fe1039b3736b06b05c348cdd64d8
wpt-pr: 15263
Automatic update from web-platform-tests
Fix BGPT backdrop-filter with opacity<1 parent
Previous to this CL, a layer with opacity<1 that contained a single compositing
child with backdrop-filter would not be properly rendered, due to an
optimization that removed the render surface for the opacity<1 layer. That
would cause the backdrop-filter to filter elements higher up the tree than it
should, due to the lack of isolation imposed by the opacity<1 layer. With this
CL, this situation is properly detected and a render surface is assigned to the
opacity<1 layer.
As part of this CL, backdrop-filter was moved from the Filter node to the
Effect node. This is required, because a single element with both opacity
and backdrop-filter need to be contained in the same node, so that the
render surface created for the backdrop filter also sees the opacity.
Bug: 497522, 836885
Change-Id: Ie6ad38231ddfda02fae8d574ca8f30d075c673e5
Reviewed-on: https://chromium-review.googlesource.com/c/1399467
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629835}
--
wpt-commits: 7c61bbcbdaebae56e093017387b21b473070bd8d
wpt-pr: 15194
Automatic update from web-platform-tests
Add support for freezing iframes
Frames that aren't loading are not visible in the viewport will be frozen
if --enable-features=FreezeFrames is provided. This will eventually be
converted to testing feature policies for frames.
BUG=907125
Change-Id: Ib0badb3f92df4ce4921dd4a4cb29c45749f64f47
Reviewed-on: https://chromium-review.googlesource.com/c/1450406
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629822}
--
wpt-commits: d31a2f38a2c7159a88ca190cde7826b91299c64f
wpt-pr: 15234
Automatic update from web-platform-tests
Use oversampling to compute frame number
When computing the frame number, round-off can happen such that the
resulting frame number is not the same as the original. To work
around this, use oversampling to compute the oversampled frame
number. Round that to the nearest frame, and then convert that back
to the desired integer frame number at the original sample rate.
This won't always work, but should make the round-off errors much less
likely.
Bug: 876917
Test: the-audiobuffersourcenode-interface/sub-sample-buffer-stitching.html
Change-Id: Id3658a986490d2aec07a382497bc24a4d99e416c
Reviewed-on: https://chromium-review.googlesource.com/c/1446869
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629697}
--
wpt-commits: 5a6917c5cb8ea8602c53fd927fe3c208bb99b463
wpt-pr: 15215
--HG--
rename : testing/web-platform/tests/webaudio/the-audio-api/the-audiobuffersourcenode-interface/resources/sub-sample-scheduling.html => testing/web-platform/tests/webaudio/the-audio-api/the-audiobuffersourcenode-interface/sub-sample-scheduling.html
Automatic update from web-platform-tests
[html] Restore utility method for query encoding
The `poll_for_stash` function was relocated from `resolve-url.js` in
service of a test refactoring [1]. However, the following tests depend
on the presence of that function in that file:
- html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html
- html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html
- html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html
Restore the function to its original location and persist the copy.
[1] https://github.com/web-platform-tests/wpt/pull/11300
--
wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8
wpt-pr: 15255
Automatic update from web-platform-tests
ReadableStream @@asyncIterator (#15097)
Test async iteration of ReadableStream.
Standard changes are in https://github.com/whatwg/streams/pull/980.
--
wpt-commits: de6f8fcf9b87e80811e9267a886cf891f6f864e0
wpt-pr: 15097
Automatic update from web-platform-tests
XMLSerializer: Fix prefix generation algorithm
Fix it in order to match to DOM Parsing and Serialization specification.
We should not expose hash values of strings.
Bug: 928639
Change-Id: I589572d87715805961f2931c6808c1bd38acade6
Reviewed-on: https://chromium-review.googlesource.com/c/1454070
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629490}
--
wpt-commits: d2c49d8610185244a31e04ef32aae70da0dd35f7
wpt-pr: 15260
Automatic update from web-platform-tests
Fix repeat spacing for 'border-image's when combined with 'round'
When either of the horizontal/vertical tile rules were 'round', we would
drop any tile spacing.
Bug: 928749
Change-Id: I6128084cdfc9e6b7604fe213d87f71b1e025d012
Reviewed-on: https://chromium-review.googlesource.com/c/1454375
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#629272}
--
wpt-commits: 77f3ead37011e5338545fe18eb9dc8a301aeda9e
wpt-pr: 15252
Automatic update from web-platform-tests
Use print() function in both Python 2 and Python 3 (#15141)
--
wpt-commits: 99b96dc0569ede4e842ec7f9c55a792df9092d9c
wpt-pr: 15141
Automatic update from web-platform-tests
Try and improve #15159 by moving the window to a deterministic location
Especially on systems where we don't have an integral scaling factor
between CSS pixels and device pixels we can end up with our ability to
resize the window depending on the location of the window.
--
wpt-commits: 71a17e293b836649a0cd7effd6ee5b89ba39414d
wpt-pr: 15222
Automatic update from web-platform-tests
Change CODEOWNERS to only cover the subtree in /css/tools
--
Add /tools/third_party to CODEOWNERS
--
wpt-commits: c70ddef5327359fe64d4b63260e5cd64c5b26db1, 5a406c55ff70128e0661209d1d169c4104d14eed
wpt-pr: 15249
On the Android 7.0 x86_64 emulator, pidof occasionally returns
no results for a running process. To guard against this case, mozdevice
retries exactly once.
Differential Revision: https://phabricator.services.mozilla.com/D20898
--HG--
extra : moz-landing-system : lando
Update the expected result of web-platform test /service-workers/service-worker/fetch-csp.https.html to FAIL
Differential Revision: https://phabricator.services.mozilla.com/D21100
--HG--
extra : moz-landing-system : lando
`InsertTagCommand::DoCommandParams()` inserts given URL to `href` of `<a>` or
`src` of `<img>`. However, it treats the given URL includes only ASCII
characters. Therefore, we cannot insert URL including non-ASCII characters
with `execCommand("createLink")` nor `execCommand("insertImage")`.
This patch makes `nsHTMLDocument::ExecCommand()` set the param as `nsString`
and makes `InsertTagCommand::DoCommandParams()` retrieve it with `GetString()`.
Differential Revision: https://phabricator.services.mozilla.com/D20615
--HG--
extra : moz-landing-system : lando
Improve support for Python 3 by running modernize over adb.py and a few other related changes.
Differential Revision: https://phabricator.services.mozilla.com/D19306
--HG--
extra : moz-landing-system : lando
The bulk of this is copy/pasted from a standard android-api-16 debug
build. The only changes are a few extra environment variables in the
taskcluster config, the subconfig file, and the mozconfig, as well as
the --enable-mozsearch-plugin flag in the mozconfig.
Depends on D20766
Differential Revision: https://phabricator.services.mozilla.com/D20767
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add .mailmap to map people to their current names
Note that this isn't used by `git log` by default (as of 2.20.1): that
depends on log.mailmap being set to true.
--
Add Tess to .mailmap
--
wpt-commits: 39f54a3dd48b560289e0f455308acf7d32fad043, f8a1bfbe5454352d3f5b58845829968ff212519b
wpt-pr: 15353
Automatic update from web-platform-tests
HTML: noreferer was never a property of hyperlinks
This should have tested the rel attribute value, but as it hasn't been doing that and it would be quite a bit of work, let's remove this instead.
--
wpt-commits: 25c665a93231027be5941838cecb3208e360d4b1
wpt-pr: 15357
Automatic update from web-platform-tests
Add screen orientation test: fire event before promise is resolved (#15267)
--
wpt-commits: 8ed64687560332642c7b34ebd16011ae5b01d99a
wpt-pr: 15267
Automatic update from web-platform-tests
XMLSerializer: Fix prefixed attribute serialization
... in a case where its owner element has xmlns:prefix of which prefix
is same as the attribute and namespace is not same as the attribute.
e.g.
el.setAttributeNS("uri1", "p:n", "v");
el.setAttributeNS(XMLNS_URI, "xmlns:p", "uri2");
ShouldAddNamespaceAttribute() checked only existence of xmlns:prefix in
the element, but we should check existence of (prefix, namespace URI)
pair in the scope according to the specification.
So, this CL adds 'recording the namespace information' step [1] defined
by the specification, and ShouldAddNamespaceAttribute() checks all
available prefixes in the scope.
[1] https://w3c.github.io/DOM-Parsing/#recording-the-namespace
Bug: 929035
Change-Id: I575e8f652ae45f7583202443cc72d5afe5faf59d
Reviewed-on: https://chromium-review.googlesource.com/c/1460643
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631058}
--
wpt-commits: 265330b7d26194cb60157a18ac399127d21f6b99
wpt-pr: 15340
Automatic update from web-platform-tests
decimal points in numbers
Tests that decimal points are allowed *before* digits (like `.1`) and *between* digits (like `0.1`), but not *after* digits (like `1.`).
Tests <https://github.com/w3c/csswg-drafts/issues/3599>
--
fix whitespace for lint
--
Name all tests uniquely
--
Merge pull request #15337 from web-platform-tests/tabatkins-patch-2
decimal points in numbers
--
wpt-commits: 5fdd036dbd18fa6d2e7cf235bd9acc625a6df22e, f17e215eaa37316f1489a7b62ab103d2a58a0d89, 31e1a1bb5fadb08749e4b8070ad0f19ec5ea1088, e2eb25aaa6dd3c512b172588f3400f9c25a410c3
wpt-pr: 15337
Automatic update from web-platform-tests
url whitespace consumption
Ensure that whitespace before or after the string in a url() results in a correct parse.
Tests https://github.com/w3c/csswg-drafts/issues/3600
--
Merge pull request #15339 from web-platform-tests/tabatkins-patch-3
url whitespace consumption
--
wpt-commits: e0b3c4cf2f69e816c6b83432968dc7fc83d700f6, 0de6fa5638c7e314a0391fae7f6bf496309fb65d
wpt-pr: 15339
Automatic update from web-platform-tests
[css-box] Inheritance, initial values (#15312)
Test that CSS Box Model properties do not inherit.
https://drafts.csswg.org/css-box-3/#property-index
--
wpt-commits: 35bd69423b10a361a969139ba0271896dced9691
wpt-pr: 15312
Automatic update from web-platform-tests
Set click count correctly to dispatch "dblclick" event
In order to dispatch the "dblclick" event to DOM by sending synthetic
mouse events, we have to check the most recent two mouse press events.
If their dispatched times and locations are close enough, we will set
the mouse event's click count to 2, which will generate the "dblclick"
event.
Bug: 606367
Change-Id: I049d6463c6bf1393c9e8b496662359eeeef7682b
Reviewed-on: https://chromium-review.googlesource.com/c/1413362
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630933}
--
wpt-commits: 1ddffbeeb6faed345ce7f999544ed1d29c7a203f
wpt-pr: 14911
Automatic update from web-platform-tests
Verify that contentDocument is updated during nested browsing context document parsing.
--
wpt-commits: ae6d56308684b97f30a01b455ce3eb205cba79aa
wpt-pr: 15268
Automatic update from web-platform-tests
Fix canonical form of rotate property.
Expected behavior is outlined in the spec here:
https://drafts.csswg.org/css-transforms-2/#individual-transform-serialization.
Summary:
* 2d serializes to just an angle.
* Axis must be specified for 3-D rotations. If the axis is parallel to the x, y or z axis, the appropriate axis name must be used.
Bug: 905274
Change-Id: I5d16f3301baf9720099e4b5b42a1b87077b97998
Reviewed-on: https://chromium-review.googlesource.com/c/1447844
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630796}
--
wpt-commits: a01ac89be3f48fa64bd96d36ac1a65ac9074eb4f
wpt-pr: 15205
Automatic update from web-platform-tests
Make stability checks provide an explicit message for duplicate test names
--
wpt-commits: 23008e948bff4c245148cfcda2ebaa72149a2bb1
wpt-pr: 15330
Automatic update from web-platform-tests
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
wpt-commits: 9a874520787308eecb14d85399cb5184efaf99ec, 999c546d4958eb649a71f0339563218a22f6d281, e032140d4ba4954c0704356f4848cc8f1d2dd590, ad09e7414f098c7833a65d336f01e76ba8c1dc15, a54f2b6ed9445d74fded895c45b561b1e7fd9314, 47bb668028ce2b7f6e564b47aee7ed12ce720532, f55469ea2fe1ed49f6b3f2d9701b793fc051bb67, 78c2264a4d9b28e89070670d6a73df470ae45aaf, 725876f98dc3fe1dd86c131b73724ac0e0a41147
wpt-pr: 15294
Automatic update from web-platform-tests
[css-grid] Overflow should be computed with the actual logical bottom
In order to compute the 'auto' height of the grid container, we set
temporarily a value based on the tracks' size. We can see this value as
a kind of 'intrinsic height'. Then, we call to the UpdateLogicalHeight
function to finally compute the grid container's actual logical height.
In order to compute the overflow area in the grid container we should
use the result of the ClientLogicalBottom function. However, we were
retrieving this value just after setting the tracks-based temporary
height, and before computing the actual logical height.
The consequence of this wrong logic is that empty grid areas may
affect the result of the ClientLogicalBottom and, as it's described
in the bug, conclude that there is a content overflow in the grid
container, even if such container has no grid items at all.
Since the grid itself is not a box, it can't contribute to the grid
container's content size; instead, its grid items should.
This change ensures that we always use the actual grid container's
logical bottom to properly compute the overflow area.
Bug: 928885
Change-Id: I05f86fbce06a83c0dbc0d5389bf0416763f8588a
Reviewed-on: https://chromium-review.googlesource.com/c/1459620
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#630735}
--
wpt-commits: aa6f52fc7b99559377c760a550e842438efa91a1
wpt-pr: 15284
Automatic update from web-platform-tests
Fix remaining preload tests flaking on wpt.fyi
This is a follow-up to https://github.com/web-platform-tests/wpt/pull/15075.
https://crrev.com/c/1436777 successfully fixed the wpt.fyi flakiness
for link-header-preload-srcset.tentative.html and
link-header-preload-nonce.html. This patch fixes that for the remaining
preload tests.
- Use step_timeout instead of dummy.js?pipe=trickle, because
dummy.js?pipe=trickle may be loaded from cache with no delay.
- Replace verifyNumberOfDownloads() with
- verifyNumberOfResourceTimingEntries() if possible
- A new helper function verifyLoadedAndNoDoubleDownload() that
doesn't fail if the resource was already cached before running
the test.
Bug: 922343
Change-Id: Ia9b7c4bd49dd76463df4607349fe4f935e5410d0
Reviewed-on: https://chromium-review.googlesource.com/c/1442020
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629029}
--
wpt-commits: eb5aa0038ee7a938beabbe4c732a685af2581dbc
wpt-pr: 15129
Automatic update from web-platform-tests
Initial support for WorkletAnimation.playbackRate
Changes for scroll-linked worklet animations will come in a separate pull request.
Bug: 852475
Change-Id: Ie6dd14242797cbc14a7e1e377f23c3dda174fe15
Reviewed-on: https://chromium-review.googlesource.com/c/1423537
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#628800}
--
wpt-commits: 9d1de21ddfa4338cfac14a887622b98207efe247
wpt-pr: 14946
Automatic update from web-platform-tests
[animation-worklet] Basic pause implementation (reland)
Pausing worklet animation now holds the time. This works as expected for main
thread animations. Implementing this for composited worklet animations will be
done in a follow up patch.
Major changes:
- Add and expose pause() method pausing the animation.
- Introduce hold_time that is used when animation is paused.
- Rework how current time is computed, it is now closer to
regular animations i.e., we either compute it based on "start time and
timeline.currentTime" or use "hold time".
- Instead of setting start time we now set the current time
which then works backward to compute either the start time or the hold time
based on the animation state.
- When transitioning animation play state, we now always set
the current time. Previously this was adhoc and inconsistent.
- Introduce has_started_ to differentiate when playing an
animation for the first time vs playing it from pause.
- Update playback_rate related calculation to use new logic.
Relanding: Original CL was reverted here [1]. Took the following steps to
address this:
- Address flakiness in unit test by using more accurate error
value matching other tests.
- Fix flakiness in layout test (worklet-animation-pause.https.html)
by using startTime and waiting for time to actually advance working around
pre-existing animation clock issue [2]. Also got rid of an invalid state
transition from pause->idle.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1434815
[2] http://crbug.com/785940
TEST:
- wpt/animation-worklet/worklet-animation-pause.https.html: js test for basic
current time calculations
- wpt/animation-worklet/worklet-animation-pause-immediately.https.html:
reftest for basic pause
- wpt/animation-worklet/worklet-animation-pause-result.https.html: reftest for
pause/resume.
- WorkletAnimationTest.PausePlay: unit test for basic state
transition and time calc
Bug: 821910,
Change-Id: I11fd2960443081be81055904d6d56a2abc3282f5
Reviewed-on: https://chromium-review.googlesource.com/c/1456640
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630548}
--
wpt-commits: 345300fad3945a5f1441fb2b2001109ca48f36e8
wpt-pr: 15279
Automatic update from web-platform-tests
[Payment Request] Add Web Platform Tests for hasEnrolledInstrument().
The failing expectations are required because hasEnrolledInstrument()
is not yet turned on by default in Blink. These tests pass when running
Chrome with --enable-features=PaymentRequestHasEnrolledInstrument.
Bug: 915907
Change-Id: I2189bfedad813e7942c7ddbd44aac78d1b895a30
Reviewed-on: https://chromium-review.googlesource.com/c/1461313
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630578}
--
wpt-commits: a7498ddcfeeca02e7b62ab9e9b359fcaa5764c62
wpt-pr: 15306
Automatic update from web-platform-tests
Deflake RTCPeerConnection-track-stats.https.html.
This CL does the following:
1. Add a test that verifies we have a succeeded candidate pair in
getStats() as soon as iceConnectionState is "connected". This is
currently flaky (https://crbug.com/926170) and marked as such.
2. Add workaround to RTCPeerConnection-track-stats.https.html so that
it does not flake due to 1), and mark it not flaky.
3. Move shared helper functions to RTCPeerConnection-helper.js.
4. Add test coverage for making sure we can become connected in the
recvonly use case. This requires changing the prefix to
".https.html" of "RTCPeerConnection-iceConnectionState".
// Already reviewed by jonasolsson@chromium.orgTBR=guidou@chromium.org
Bug: 922955, 926170
Change-Id: I828e46273a84447c817595a466a5e143bde30eca
Reviewed-on: https://chromium-review.googlesource.com/c/1442201
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627421}
--
wpt-commits: 7179024d5dfb231073c7319948499d7e30f671cb
wpt-pr: 15133
Automatic update from web-platform-tests
Update dynamic import tests for HTML event handler changes
Fixes https://github.com/web-platform-tests/wpt/issues/15183. Follows https://github.com/whatwg/html/pull/4302.
This updates paths/expected nonce behavior now some methods of loading are not based off the current script.
--
wpt-commits: 8ecb503bc748ded75e7f5c224b95344a2966eeb9
wpt-pr: 15251
Automatic update from web-platform-tests
Remove OriginalTimingAllowOrigin from ResourceTimingInfo
The OriginalTimingAllowOrigin attribute was added in
https://codereview.chromium.org/271083002 to ensure TAO headers are
preserved on cached resources (304 responses). This CL removes it
because it seems that it is no longer needed. It also moves the
corresponding test to WPT.
Bug: 929453
Change-Id: I41e0c84b04a94acc27c22e375f55398d9fc411e5
Reviewed-on: https://chromium-review.googlesource.com/c/1459333
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630441}
--
wpt-commits: f84a067164651cc9069c36d6098d6a6b03d63816
wpt-pr: 15300
Automatic update from web-platform-tests
[css-overscroll-behavior] Computed values (#15287)
The computed values of the overscroll-behavior-x and overscroll-behavior-y
properties are the keywords as specified.
https://drafts.csswg.org/css-overscroll-behavior/#property-index
--
wpt-commits: 374bcf2e5aa678ce021ea8e8d0872114b9fd1acf
wpt-pr: 15287
Automatic update from web-platform-tests
[Payment Request][WPT] Fix canMakePayment() tests.
Before this patch, a couple of WPT test cases for canMakePayment() would
fail when attempting to issue an automated click with a user gesture to
to show the payment sheet.
This patch splits the test cases that need user gestures into a manual
test that solicits a real user gesture click to show the payment sheet.
After this patch, the canMakePayment() tests are passing.
Bug: 929773
Change-Id: Ide9a310f39c69957b2b182f00e6db37ea6391e12
Reviewed-on: https://chromium-review.googlesource.com/c/1459061
Reviewed-by: Danyao Wang <danyao@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630358}
--
wpt-commits: 7d5d8b89aba590b018d7ac402c233df89b42dcbd
wpt-pr: 15281
Automatic update from web-platform-tests
Round up to the next render quantum for suspend
OfflineAudioContext.suspend rounds the time up to the next render
quantum instead of down. It is sometimes confusing when suspend
occurs before the given time, which is different from how everything
else works in WebAudio.
A few tests need to be fixed because they computed the boundary by
rounding down instead of up. One test needed to be adjusted because
the times were rounded to different boundaries instead of the same
boundary.
See also https://github.com/WebAudio/web-audio-api/issues/1822
Bug: 927895
Change-Id: Ie6685c620dd38eb2a059901d13b907764ba1a2db
Reviewed-on: https://chromium-review.googlesource.com/c/1450536
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630346}
--
wpt-commits: 1b1a627e597f15b60327191799b8081beac2a3cd
wpt-pr: 15214
Automatic update from web-platform-tests
Add an id="log" container at the top of the page for MathML testharness tests. (#15298)
Currently the test summary is appended at the end of the page, sometimes after
a lot of MathML formulae. Adding an id="log" container allows to display the
summary at the top of the page.
--
wpt-commits: e2dd57c3f273468b3c6a087978c531dcd00933de
wpt-pr: 15298
Automatic update from web-platform-tests
Remove two uses of dedicated-workers.idl (#14952)
Prerequisite for https://github.com/web-platform-tests/wpt/pull/12803.
--
wpt-commits: 45b6a5be22e5ea7596c55f5d1e65bae5e62e1656
wpt-pr: 14952
Automatic update from web-platform-tests
[Background Fetch] Fix flaky WP test that's timing out.
Due to the scheduler handling multiple requests, there is an issue where
the in-progress processed bytes are being overwritten.
This CL fixes the test by not relying on that value. The underlying
issue will be fixed in a follow-up CL.
Bug: 929929
Change-Id: I48a1d7bb3899c441cdbf8dd2c13623204c1b9213
Reviewed-on: https://chromium-review.googlesource.com/c/1460924
Reviewed-by: Mugdha Lakhani <nator@google.com>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630316}
--
wpt-commits: 7451c0c0cf527c8a91e56e539fad31f50356d494
wpt-pr: 15295
Automatic update from web-platform-tests
Use CSS style to set color of text and background. (#15297)
Currently, many tests unnecessarily rely on the MathML mathcolor/mathbackground
attributes to be implemented. This commit use the equivalent CSS color and background properties instead, except for the test that actually checks support for the MathML color attributes (relations/html5-tree/color-attributes-1.html).
--
wpt-commits: 4ec94cca5a27b65c5eb7ef3910a6a94c3b610597
wpt-pr: 15297
Automatic update from web-platform-tests
HTML: restore coverage for query encoding
When the query encoding navigation tests were refactored to use WPT's
"variant" feature [1], the new structure omitted one of the encodings
which was previously tested. Although the encoding will be used when a
variant is not specified, the automation tooling only uses variants
which are explicitly specified. This can be observed through the
`--list-tests` flag of the `wpt run` command:
$ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html
/html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8
/html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251
Explicitly declare the default variant, restoring the original test
coverage.
[1] https://github.com/web-platform-tests/wpt/pull/11300
--
wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3
wpt-pr: 15256
Automatic update from web-platform-tests
Async Clipboard: Integrate readImage/writeImage into generic read/write
- read/write now use Blobs instead of DataTransfer, and can only read/write one
type at a time.
- read/write can now read/write images in addition to existing text support.
- readImageExperimental and writeImageExperimental removed.
- Images will be encoded in the same manner as before this CL, whereas text
will be emitted with utf-8 encoding.
- read will prefer to return an image if one is available, and will return text
otherwise.
- Relevant tests updated.
Future Work:
- Use vectors or lists or some collection of Blobs to read/write many types at
a time, to work towards feature parity with DataTransfer.
Bug: 916823, 150835
Change-Id: I89d12ba137954731acb7180ac2fb6d15b0c264ae
Reviewed-on: https://chromium-review.googlesource.com/c/1435220
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630205}
--
wpt-commits: 305e84c0138382fcc1169e76f53173a4330786cb
wpt-pr: 15091
Automatic update from web-platform-tests
[serial] Implement feature policy checks
This API should follow the example of WebUSB and require explicit
authorization via feature policy when used in a cross-origin iframe.
Bug: 884928
Change-Id: Ia953c86a45e8b38b901b790b8aee912fd991e1a1
Reviewed-on: https://chromium-review.googlesource.com/c/1392357
Reviewed-by: Luna Lu <loonybear@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Oliver Chang <ochang@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630196}
--
wpt-commits: 5041c80124749711b4f143c2136903e84ad42ad1
wpt-pr: 14686
Automatic update from web-platform-tests
Use gPV/sP, as that's slightly more well-supported
Requested by @emilio in <https://github.com/w3c/csswg-drafts/issues/3588#issuecomment-460019494>
--
Merge pull request #15286 from web-platform-tests/tabatkins-patch-1
Use gPV/sP, as that's slightly more well-supported
--
wpt-commits: f912ea28e7a5451f51d38d62cd0aee489618e4cb, ead8f8b00d0b68237109f3c93d0ccae076a34f98
wpt-pr: 15286
Automatic update from web-platform-tests
[Payment Request][WPT] Fix show() tests. (#15285)
Before this patch, the WPT tests for PaymentRequest.show() failed (and
were expected to do so) because the tests run in a content shell, which
does not have the Payment Request components sufficient for showing a
browser payment sheet.
This patch converts the show() test into a manual one, which should be
run in a full browser. One test case remains automated, because its
intent is to invoke show() without a user gesture. That test case is
expected to fail because Chromium does not require a user gesture for
show() at this time (https://crbug.com/817807).
After this patch, the manual WPT tests for PaymentRequest.show() pass in
the full Chromium browser.
Bug: 929773 817807
Change-Id: I9cacb5447fb3ae43a8b50c53a74b7c58db8f4466
--
wpt-commits: 9cd1c2970839f44d1d2fb0f6e862d4b05a1065ce
wpt-pr: 15285
Automatic update from web-platform-tests
[Payment Request][WPT] Fix abort() tests. (#15283)
Before this patch, the WPT tests for PaymentRequest.abort() were
expected to fail due to including the vendor testdriver JavaScript file
before the generic testdriver file. The vendor file was attempting to
use the objects defined in the generic file, but the incorrect include
order caused a JS error.
This patch reorders the vendor JS file to be after the generic JS file
and splits out the manual tests that require a user gesture for
PaymentRequest.show().
After this patch, the PaymentRequest.abort() tests are passing.
Bug: 929773
Change-Id: Ic0f8ff84b478116821e98775d1cec31cfad32d9f
--
wpt-commits: ba78e657cbc2648e1540216e5a7973bc91f221f0
wpt-pr: 15283
Automatic update from web-platform-tests
Do not require user gesture if pictureInPictureElement is set
Following https://github.com/WICG/picture-in-picture/issues/116, it
would be great to allow video to enter Picture-in-Picture without user
activation if there's already a visible PiP window in the context of the
document, in other words if `document.pictureInPictureElement` is set.
Bug: 928697
Change-Id: I2c191368d8dd1bd6ddade719399d0679ef410575
Reviewed-on: https://chromium-review.googlesource.com/c/1454360
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630026}
--
wpt-commits: 5692bc8fe5e5ae3703dda9f0689e1d8ec3431411
wpt-pr: 15247
Eric Willigers
Tab Atkins Jr
Blink WPT Bot
moz-wptsync-bot
François Beaufort
Nicolas Pena
Brandon Jones
Jordan Taylor
Geoffrey Sneddon
Dominic Farolino
Mason Freed
Kent Tamura
Dave Tapuska
L. David Baron
Raymond Toy
Peter Van der Beken
Mike Pennisi
Mattias Buelens
Yashar Dabiran
Fredrik Söderquist
cclauss
Brindusan Cristian
Andrea Marchesini
Byron Campen [:bwc]
Cosmin Sabou
Geoff Brown
Emilio Cobos Álvarez
Nika Layzell
Alexander Surkov
arthur.iakab
Mike Conley
Ryan Hunt
Andreea Pavel
Narcis Beleuzu
Eden Chuang
Oana Pop Rus
Gurzau Raul
Masayuki Nakano
Dorel Luca
Jonathan Kingston
Tom Prince
Noemi Erli
Razvan Maries
Ciure Andrei
Kartikaya Gupta
Coroiu Cristina
Mats Palmgren
Dave Hunt
Csoregi Natalia
Anne van Kesteren
pyup.io bot
Johanna
autofoolip
Xianzhu Wang
Lan Wei
Josh Matthews
Kevin Ellis
James Graham
Javier Fernandez
Kunihiko Sakamoto
Olga Gerchikov
Majid Valipour
Danyao Wang
Henrik Boström
Jon Coppeard
Rouslan Solomakhin
Frédéric Wang
Philip Jägenstedt
Rayan Kanso
Darwin Huang
Jacob DeWitt
Reilly Grant