Automatic update from web-platform-tests
[Azure Pipelines] drop references to 'Hosted Windows Client Next' (#20334)
We don't use this anymore.
--
wpt-commits: 41c8e340efa48f39526da219d4fedebe1ec5ff1f
wpt-pr: 20334
Automatic update from web-platform-tests
reference all css grid tests to css/support/grid.css and eliminate local duplicates of grid.css (#20337)
--
wpt-commits: 4e30ebf34fd076f7b44ef4bfa6165a61121270eb
wpt-pr: 20337
Automatic update from web-platform-tests
Reassign snap areas when adding snap container
Making a container scrollable should make it a valid snap container.
In doing so, any descendant snap area that should be assigned to the
container should be reassigned as such.
Bug: 1007456
Change-Id: Iccd220311ce592f921dc8424780632e499d3201c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900920
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Kaan Alsan <alsan@google.com>
Cr-Commit-Position: refs/heads/master@{#717011}
--
wpt-commits: 5b9f9a0d1be1e14cc222cfbc6069fc70cd5d2f8e
wpt-pr: 20151
Automatic update from web-platform-tests
[Background Sync] Update WPT tests.
This CL:
1. Factors out Periodic Background Sync WPT tests in a separate directory
2. Adds a separate idl harness test for Periodic Background Sync,
3. Fixes a bug in periodicsync.https.window.js, in the setting of the scope.
Bug: 996664
Change-Id: I8653e8030880aa893d5d01e053b248828f88bbfc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1924196
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Auto-Submit: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#717007}
--
wpt-commits: c42db5468b46bbf47b52a74fbcc9073980a39560
wpt-pr: 20319
Automatic update from web-platform-tests
Media Capabilities: make framerate a double instead of a DOMString.
Spec change: https://github.com/w3c/media-capabilities/pull/128
Bug: 994017
Change-Id: Iab036264fe19a6676c97bb12648321408d91f283
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755046
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716773}
--
set timeout to long
--
wpt-commits: 36691d0c57c84b80236ed53105ea15afaa7d88aa, 21423802c95e1b800b07e71c6f19a923f7d16616
wpt-pr: 18440
Automatic update from web-platform-tests
Chromedriver] Fix PerformAction to support multi touch points cases (#20276)
* Chromedriver] Fix PerformAction to support multi touch points cases
For the multiple touch points case, if we have one point move and the
other point stay still, such as
point 1: pointerdown, pause, pointerup
point 2: pointerdown, pointermove, pointerup
We should send five touch point events of "pointerdown", "pointerdown",
"pointermove", "pointerup", "pointerup" with pointer id 1, 2, 2, 1, 2.
Bug: 1020674
Change-Id: I7bdb49b7b37d4f83ef976750e106cbd27afc9e74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900632
Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#715739}
* add expectation data
* rename to ini
--
wpt-commits: df29f11cf0686caced7f382bcaff059c4dbfc070
wpt-pr: 20276
Automatic update from web-platform-tests
service worker: Use the correct spelling for referrer in a wpt test (#20341)
--
wpt-commits: 58ecdcd7891483de0942c4e017d4e9bf202d78c7
wpt-pr: 20341
Automatic update from web-platform-tests
bindings: Do not access @@iterator twice when converting union to sequence
A rough approximation of https://heycam.github.io/webidl/#es-union when
trying to convert an ES value to an IDL sequence or frozen array is:
1. Call the GetMethod abstract ES operation to retrieve the @@iterator
property.
2. If it is not undefined, invoke
https://heycam.github.io/webidl/#create-sequence-from-iterable with the
ES value and the method obtained above.
So far, we were implementing it roughly like this:
1. Call the GetMethod abstract ES operation to retrieve the @@iterator
property.
2. Invoke https://heycam.github.io/webidl/#es-sequence with the ES value,
which disregards the method obtained in step 1 and goes through the whole
process of calling GetMethod again and using that to create a sequence
from an interable.
This is obviously not compliant with the spec, and the multiple calls to the
GetMethod abstract operation are user-visible, as can be seen in the test
case attached to the bug 1024388.
Properly fixing this requires changes to a few different classes and
functions:
* Make HasCallableIteratorSymbol(), which is called by the overload
resolution algorithm implementation, be a small wrapper around
GetEsIteratorMethod(). While HasCallableIteratorSymbol() precedes
GetEsIteratorMethod(), the latter's implementation is more spec-compliant.
* Add a move constructor to ScriptIterator, as well as a static method that
can create a ScriptIterator out of an ES value by invoking
GetEsIteratorMethod() and GetEsIteratorWithMethod() underneath.
* Make NativeValueTraits<IDLSequence<T>>::ConvertSequenceSlow() take a
ScriptIterator rather than a v8::Local<v8::Object>, which allows us to
delegate getting an iterator out of an iterable object to the static
ScriptIterator method mentioned above. This also helps reduce the size of
the generated per-type NativeValueTraits<IDLSequence<T>> template code.
* Analogously, invoke ScriptIterator::FromIterable() in the union conversion
code, and invoke a new NativeValueTraits<IDLSequence<T>>::NativeValue()
overload that takes a ScriptIterator, so that we do not access the
@@iterator property multiple times in the union conversion code.
Bug: 1024388
Change-Id: I47e6c0ca881e6e77f883ee78b5e1611138cdcc4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917169
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716960}
--
wpt-commits: 6261dbb7e6c573eaac487db671d8ee8dc76f0dea
wpt-pr: 20318
Automatic update from web-platform-tests
[webnfc] Make NDEFReader#scan() return a Promise
Previously NDEFReader#scan() returns void and an NDEFErrorEvent will be
dispatched in case that the scan operation cannot be started
successfully.
This is not a well accepted pattern, and also to align with
NDEFWriter#push(), this CL makes NDEFReader#scan() return a Promise
instead.
Note that now NDEFErrorEvent is only used to notify Mojo disconnection,
a follow-up CL will remove it completely by using ErrorEvent instead.
The spec change:
https://github.com/w3c/web-nfc/pull/398https://github.com/w3c/web-nfc/pull/432
BUG=520391
Change-Id: I1477258ab70f7e40da31ea8795d63125b6a13af0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899586
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716904}
--
wpt-commits: 581a056bf7a743722a2e83cb80e1a8ce250e4f9d
wpt-pr: 20193
Automatic update from web-platform-tests
[webnfc] Use one nfc mock object per test file
Previously, each run of nfc_test() creates a new nfc mock object in the
start and destroyes it in the end.
Considering a test file containing multiple nfc_test() runs, in Blink we
have just one NFCProxy instance per page context to talk to these mocks,
that means our NFCProxy gets a broken NFC Mojo connection each time the
previous nfc_test() runs to the end then has to reconnect to another new
nfc mock for the coming nfc_test().
This is unnecessary and does not align with the product code logic that
always keeps one NFC Mojo connection alive per page context, unless
something unexpected happens in Device Service.
Also, this makes it easier for a nfc_test() to interfere with the next
one, e.g. a nfc_test() ends and closes the NFC Mojo connection, the
disconnection message will arrive at our NFCProxy asynchronously and we
can not have any assumptions on the arrival time, assuming it's still on
the way and the next nfc_test() has already started, at that point our
NFCProxy has no idea that the current Mojo connection was already closed
but continues to talk to it.
This CL makes one nfc mock object be reused throughout one test file to
address the above concerns.
BUG=1019663
Change-Id: I7e2ae9816936081e1f59688652e34b35a5295af6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913588
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716874}
--
wpt-commits: 5980fe965255f86a1ee2fa698e06047576840640
wpt-pr: 20227
Automatic update from web-platform-tests
Add an extra test to check that inert propagates into Shadow DOM as well as out via slots
Bug: 692360
Change-Id: I8e24c36fbc6b476cfb1f08c0c07b890487995a39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918793
Commit-Queue: Alice Boxhall <aboxhall@chromium.org>
Reviewed-by: Meredith Lane <meredithl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716831}
--
wpt-commits: 3753e6678af4e2440b625cd104f6330c1e93a16d
wpt-pr: 20267
Automatic update from web-platform-tests
Plumb outside settings object for ServiceWorkerRegistration#update()
This is similar to crrev.com/c/1861294 but for update(). Script
fetches for update check happen on the browser and are managed
by ServiceWorkerUpdateChecker so pass some information to
ServiceWorkerUpdateChecker too.
This CL has a behavioral change. The 'Referer' header of the request
triggered by update() in a document/service worker will be changed.
Before this CL it was the url of the top-level script but after this
CL it is document/service worker's url. This behavior is consistent
with the spec.
Bug: 937177
Change-Id: I57e9ce7c91a748ad549a49e4e46c7890dcca2903
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1905028
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716516}
--
Mark referer-toplevel-script-fetch.https.html as slow
--
wpt-commits: b9fcfe91bc700f21ef08b44fb9dac562eb68495f, 295f22bfeb7e6db748e6b0e28c31adfeb498b55d
wpt-pr: 20170
Automatic update from web-platform-tests
[ResourceTiming] Add test for new TAO check (#20320)
This CL modifies the tests as follows:
* '*' is now the default TAO header. This means most sandwich tests use '*'.
* Another resource is added to crossorigin-sandwich-TAO to test the case in
which the header is the page origin, and this should now fail (this was the
test before this CL).
* The resources in crossorigin-sandwich-TAO are changed to images because it's
not super clear how iframes will be handled.
Bug: 1022816
Change-Id: I2110653a5240cff825d3130cfe6dc64e8d2f8e23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1924635
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716652}
--
wpt-commits: cd51095ccff19a22f742a4081db89fd015db5d7b
wpt-pr: 20320
Automatic update from web-platform-tests
Use existing external resource for <use> while revalidating
When we load a previously cached resource for <use> and it requires
revalidation - and an earlier <use> that references the same resource
hasn't yet generated its shadow tree - we could end up failing to
generate a shadow tree for the the "first" <use> since the resource
appears to be "invalid" while the revalidation is in progress. This
"first" <use> would then not be invalidated when the revalidation
completes.
Consider the resource to be valid while revalidating if it has a
Document already - meaning it has previously finished loading and
successfully parsed a document. This means the "first" <use> might end
up being stale until it's invalidated if the revalidation returned a
newer version of the resource - which is wrong but arguably better than
failing to display at all like was the case previously. (This should
also be consistent with how other types of resources are handled in
cases like this.)
Bug: 593261, 1021530
Change-Id: I9d68a1a60685757a990c2ec811c5ca53afc4fb25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903200
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716678}
--
wpt-commits: b281a06110c196a820b789201ab8793bbef0219a
wpt-pr: 20150
Automatic update from web-platform-tests
Removed unused `platform_ini` member in browser.py
--
wpt-commits: a93b1f7d58ed6456636ab3af5ef178f2d5d51893
wpt-pr: 20316
Automatic update from web-platform-tests
Test for link element firing multiple events (#20301)
--
wpt-commits: ee893908a206f562a35f202fce67e667bc19f603
wpt-pr: 20301
Automatic update from web-platform-tests
[Trusted Types] Cover attribute node manipulation with Trusted Types checks.
Element::setAttribute will perform trusted types checks, which (currently)
can be circumvented by obtaining the DOM's attribute node and setting the
value directly. This fixes this bypass, by performing identical checks when
the attribute node values are set, and/or the attribute node is attached to
an element.
Bug: 1008012
Bug: https://github.com/w3c/webappsec-trusted-types/issues/47
Change-Id: I1d8ead85b3fa11821c329e1f4af60c1e85ea8298
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1911215
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716193}
--
wpt-commits: 36362f1a77faf18831c8b596e7b5bee081629817
wpt-pr: 20228
Automatic update from web-platform-tests
Move the pointerevents extension tests to the main
Move the pointerevents extension tests to the main
folder following the spec merge.
Change-Id: I0b91fb0760cf36ce36e8ba988367878d427bd08d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906903
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#716187}
--
wpt-commits: 2eac98679d83cef15ddb02292aad2f1ddb8a004c
wpt-pr: 20202
Automatic update from web-platform-tests
Change `sec-fetch-mode` from `no-cors` to `navigate` for <embed> / <object>. (#20251)
See https://github.com/whatwg/fetch/pull/948 .
Bug: 1011724
Change-Id: I546752f3d0120f71cc810bfb17f960789e6c53dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917259
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Yifan Luo <lyf@google.com>
Cr-Commit-Position: refs/heads/master@{#715664}
--
wpt-commits: bddf074a0c1b8d10c5d6e4b3d151e1612178f7a2
wpt-pr: 20251
Automatic update from web-platform-tests
Fix failing Fetch Metadata WPT (#20230)
See https://wpt.fyi/results/fetch/metadata?label=experimental&label=master&aligned.
1. `xslt.tentative.https.sub.html`: delete tests for same-site and cross-site, because these requests are not allowed and has been blocked by browser behavior.
2. `redirect/multiple-redirect-https=downgrade-upgrade.tentative.sub.html` and `redirect/redirect-http-upgrade.tentative.sub.html`: removed from `NeverFixTests` and change the expectation for mode from `nasted-navigate` to `navigate`.
3. `redirect/redirect-https-downgrade.tentative.sub.html`: removed from `NeverFixTests` and change the expectation for Https downgrade script.
Bug: 1024198
Change-Id: Ia0cf0ccc2bef38c4525bebab0a050e7b1de9a5e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912712
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Yifan Luo <lyf@google.com>
Cr-Commit-Position: refs/heads/master@{#714940}
--
wpt-commits: dfab246b15077e1d3740a222c25eef112cfd20d4
wpt-pr: 20230
Philip Jägenstedt
_Ros_
Kaan Alsan
moz-wptsync-bot
Mugdha Lakhani
Mounir Lamouri
Blink WPT Bot
Stephen McGruer
Raphael Kubo da Costa
autofoolip
Leon Han
David Grogan
Alice Boxhall
Kenichi Ishibashi
Xiaocheng Hu
Fredrik Söderquist
pyup-bot
Dominic Farolino
Emilio Cobos Álvarez
TAMURA, Kent
Daniel Vogelheim
Navid Zolghadr
James Graham