Automatic update from web-platform-tests
[webnfc] Introduce IDLs for NFCReadingEvent and NFCReadingEventInit.
This CL introduces IDLs for NFCReadingEvent and NFCReadingEventInit
interfaces, and updates the baseline of relevant wpt tests.
http://w3c.github.io/web-nfc/#dom-nfcreadingevent
The corresponding spec changes were introduced in
https://github.com/w3c/web-nfc/pull/179https://github.com/w3c/web-nfc/pull/227
BUG=520391
Change-Id: If2090d73ce746208a9e535fe31b6d52a9940d2fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655092
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679910}
--
wpt-commits: 239561ebf7630cd4419dc8cea83606f27062bf87
wpt-pr: 17410
Automatic update from web-platform-tests
Implement QueuingStrategies in C++
Implement CountQueuingStrategy and ByteLengthQueuingStrategy in C++.
Implementing in WebIDL leads to some changes in semantics:
1. highWaterMark is now a getter on the prototype rather than an
property on each object. This is because adding properties directly on
objects is not usual practice in WebIDL, and is problematic to implement
in Blink.
2. size() is now a function returned by a getter. This is because a
methods in WebIDL must be called with |this| set to a valid object of
the appropriate type, but size() is called with |this| set to undefined.
See https://github.com/whatwg/streams/issues/1005 for more discussion.
These aren't expected to change behaviour of code in the wild, but the
count-queuing-strategy.any.js and byte-length-queuing-strategy.js
tests detect it.
Also add tests that subclassing of CountQueuingStrategy and
ByteLengthQueuingStrategyworks works properly. A previous iteration
of this change broke it.
Bug: 981333
Change-Id: Ifc18a469a58f73d54563ca549a1c8db0e001303b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692108
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679897}
--
wpt-commits: 4dbc86fa9b79da17a037140fc2eaba05c80f90ee
wpt-pr: 17804
Automatic update from web-platform-tests
[css-text] avoid invisible spaces at the end of a line (#17954)
--
wpt-commits: 842f491badfe8be10cb741c65672230fabb3fbdf
wpt-pr: 17954
Automatic update from web-platform-tests
Add coordinate test for scrollLeft and scrollTop (#17971)
This test the assigned and extreme value of scrollLeft and scrollTop in different combination of writing-mode and CSS direction.
--
wpt-commits: 8cee348e6fe3c77042e1c3a21f766c5e81c85913
wpt-pr: 17971
Automatic update from web-platform-tests
A test to check if service worker can be updated when the script shrinks
Bug: 986688
Change-Id: I8f669c43120fea64dc7b856934e4f2e3198b998d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1712954
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679889}
--
wpt-commits: a04bcd452ecf99580ea4557fe3c4b2db42bc27b4
wpt-pr: 17993
Automatic update from web-platform-tests
Update internal XR Layout tests to match external WPTs
Several updates to xr-test-utils to make it more closely align with
webxr_utils:
* Each xr_session_promise_test only runs one sessionMode
* xr_session_promise_test now sets the baseLayer on the session so that
tests don't have to
New parameter added to both test functions "sessionObjects", which
currently just passes the gl/glLayer down for those tests to access, but
which can be expanded for any other objects that the boilerplate creates
that need to be passed down.
Future work will remove the other helpers from xr-test-utils, though due
to paths for imported scripts, unless internal tests are moved to
wpt_internal it may not be possible to consolidate to use webxr_test.js
Bug: 981003
Change-Id: Ibc36a4eb897d834643a3e604a6e79fc7264b5e4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1707590
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679770}
--
wpt-commits: 7d6b3d3b1f01873f67f2a5000e247c94d0c9a68d
wpt-pr: 17896
Automatic update from web-platform-tests
[animation-worklet] Implement getComputedTiming() in worklet scope
Calling effect.getComputedTiming() in worklet scope now returns a
valid computed timing based on the effect local time. To enable
this we make the following changes:
Moved getComputedTiming() logic from AnimationEffect to Timing
to enable sharing it in AnimationEffect and WorkletAnimationEffect
Re-implement logic to calculate computed timing based on specified
timing and local time.
Update WorkletAnimationEffect idl to add the new method
Add basic test for getComputedTiming function
Bug: 915344
Change-Id: I8783e4b3716c2142314e7c1e4d81ec8e1a06e04e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636455
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Jordan Taylor <jortaylo@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#679174}
--
wpt-commits: 156702347a8b60e8e99d977d2b0cca9dc2a57608
wpt-pr: 17109
Automatic update from web-platform-tests
[css-properties-values-api] Fix handling of 'em' unit cycles.
We would incorrectly trigger fallback behavior inside the cycle, which
is not correct. Additionally, the custom property responsible for the
cycle would get 'unset' behavior, which is not correct for custom
properties in a cycle. They should become "invalid at computed-value
time", not unset.
Change-Id: I3865e1c17da06fe7688d2760bde120abff990d85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708073
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679505}
--
wpt-commits: dfac707fc3589d1ef088620111d3ea065f47e472
wpt-pr: 17967
Automatic update from web-platform-tests
Cookie Store API: Use async add_cleanup() in tests.
testharness.js now supports asynchronous cleanup logic so this CL
replaces all usage of the async_cleanup() workaround with
add_cleanup().
GitHub issue: https://github.com/web-platform-tests/wpt/issues/13127
Bug: 729800
Change-Id: Ic2c2ca7c8f839fc42481b1833071b74416611d92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710770
Commit-Queue: Staphany Park <staphany@chromium.org>
Auto-Submit: Staphany Park <staphany@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679465}
--
wpt-commits: 8de705e2b444ff704ed80b3f29f58ec9d9dcee22
wpt-pr: 17949
Automatic update from web-platform-tests
LazyLoad: Add test for deferred iframes using attributes at parse time
This CL adds tests for base URL and referrer-policy state at parse time
are retained when the deferred frame is loaded-in.
Bug: 984983
Change-Id: Iaea240cf54b6b4e6977c129fcea971051d5900d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708293
Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679460}
--
wpt-commits: 55e4f13e9fd0c15c1eac422e76aeb1f904026ea3
wpt-pr: 17905
Automatic update from web-platform-tests
Unbreak RTCPeerConnection-getStats
This allows RTCPeerConnection-getStats to complete even though we do
not send an unmute event when tracks are getting data.
Bug: chromium:986045
Change-Id: Ic7716af58953e3038ba4f2747d8bf94dfee0e2a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710576
Reviewed-by: Steve Anton <steveanton@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679394}
--
wpt-commits: 9e35608dc88f4601ecd8bbc0d020ace897423ef3
wpt-pr: 17959
Automatic update from web-platform-tests
[css-text] Add test for text-transform:fullwidth and space collapsing (#17956)
--
wpt-commits: 1eb5d0b60485622d358a543ff832b09605feef42
wpt-pr: 17956
Automatic update from web-platform-tests
Make XSLT IDL source and idlharness.js test tentative (#17917)
* Rename xslt.idl to xslt.tentative.idl
This is to avoid it being removed by the reffy-reports sync process:
https://github.com/web-platform-tests/wpt/pull/17847
* Update and rename idlharness.window.js to idlharness.tentative.window.js
--
wpt-commits: 91fd78875c637702d8f30b95298b52fbec7cfdd2
wpt-pr: 17917
--HG--
rename : testing/web-platform/tests/interfaces/xslt.idl => testing/web-platform/tests/interfaces/xslt.tentative.idl
Automatic update from web-platform-tests
Tweak invalid-src.html to avoid harness timeout
In the test:
wpt/html/semantics/embedded-content/the-img-element/invalid-src.html
the test ends up waiting indefinitely for a 'loadend' that never arrives
(or is dispatched). Since 'error' (or 'load') and 'loadend' is always
fired in the same task (when both are fired), we can set a timeout to a
following task and avoid the harness timeout.
Bug: 627706
Change-Id: Ia9f27d5549a14509a3bbf71f28366c9e5d76fc8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710541
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679246}
--
wpt-commits: c23028ea6703236331a486258ba9a7a750e86722
wpt-pr: 17935
Automatic update from web-platform-tests
[css-align] Computed values for align*, justify*
Computed values are as specified, with an exception for justify-items:
"If the legacy keyword appears on its own (without an accompanying
left, right, or center keyword): if the inherited value of
justify-items includes the legacy keyword, this value computes to
the inherited value; otherwise it computes to normal."
https://drafts.csswg.org/css-align-3/#propdef-justify-items
Change-Id: I61a4baba66d32aad9d7eb3b0e62d316a31bcb18d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1699263
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Chris Nardi <cnardi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679232}
--
wpt-commits: 9b5ea6f93a62f72fdcaa94ba11d0233a8e8c633f
wpt-pr: 17800
Automatic update from web-platform-tests
Only update AnimationClock when rendering lifecycle updates.
Previously we updated the AnimationClock any time the current time was
asked for outside of a rendering lifecycle update by guessing at what
the next rendering lifecycle time would be. It was possible, even quite
likely, for this time to get ahead of the next actual frame time. By
spec the DocumentTimeline should only update when the rendering
lifecycle is updated [1].
[1] https://drafts.csswg.org/web-animations/#timelines
Bug: 785940
Change-Id: I11971a5344013bb99cdcbbd7cfc1ad3480d4c633
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1704389
Commit-Queue: Robert Flack <flackr@chromium.org>
Auto-Submit: Robert Flack <flackr@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679216}
--
wpt-commits: dec9cf8d3b56e4b72da3f693b91989484f2353f3
wpt-pr: 17888
Automatic update from web-platform-tests
Update rejects_if_not_active.https.html (#17920)
Use a second payment sheet to detect that the first payment sheet is dismissed as a result of navigation instead of relying on the rejection of the first promise, which may never settle in some implementations (i.e. Blink).
--
wpt-commits: ba57a8dec15e0004616e37853865d1a2eb6cda7e
wpt-pr: 17920
Automatic update from web-platform-tests
[Media Session] Implement "seekto" in Blink
Implement "seekto" action for media session in Blink.
Also implements MediaSessionActionDetails which were
added as part of the same spec change.
BUG=977375
Change-Id: I8a95ebfd8390922e152117d26c2cbb20889c0c9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696204
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679198}
--
wpt-commits: 9501ee7f29d8ad85fe2ea4fd156b5631c0e0eac8
wpt-pr: 17776
Automatic update from web-platform-tests
Add requestSession(..., XRSessionInit) arg, fix webxr_utils.js
This doesn't do anything yet, enforcing required features and verifying that
features used were requested is being added in followups. For now, add WPT
tests to exercise this, marking the not-yet-supported parts as expected
failures.
Update existing tests to request features for reference spaces that aren't
available as default features for the given session mode. Otherwise they
are supposed to be rejected according to the latest WebXR spec.
Also fix a bug in webxr_utils.js. If a requestSession was successful despite
being expected to fail, its session cleanup wasn't properly sequenced and
happened after the next test had already started, leading to unexpected
collisions such as no devices being available.
Bug: 985095
Change-Id: I8eafdf7739dc9d66e85723ca3c39015bb307450d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1707830
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679187}
--
wpt-commits: 20769798163dfce426122c500f8a84e67d8780d7
wpt-pr: 17898
Automatic update from web-platform-tests
[CSS] Treat viewport-relative units as computationally independent
According to spec (*):
"A property value is computationally independent if it can be converted
into a computed value using only the value of the property on the
element, and 'global' information that cannot be changed by CSS."
Therefore, viewport-relative length units should be treated as
computationally independent. This patch fixes the implementation to
comply to that.
(*) https://drafts.css-houdini.org/css-properties-values-api-1/#computationally-independent
Change-Id: Ib75a1981aa4083ee68cef8ba0bbc58d557cd663c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710090
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679183}
--
wpt-commits: 6792d16f8eb649aacee0c7b0447649e3d4bc2771
wpt-pr: 17927
Automatic update from web-platform-tests
Guard LayoutInstability and EventTiming tests on interface
Most tests make use of PerformanceObserver, which means that they will
timeout if the interface is not supported. Thus, add a check to bail out
early in those cases instead. In the future, once suppportedEntryTypes
is supported for major browser vendors we could replace the check by
invoking that method.
Change-Id: I2df430e92a47876d3b38bb016bfc8d2a601e6ff5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1707997
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679090}
--
wpt-commits: 32a1ff65b818e5941d1f457df2c162d766cd9ac6
wpt-pr: 17914
Automatic update from web-platform-tests
Add buffered flag tests for LongTasks and NavigationTiming
This CL adds tests using a couple of PerformanceObservers to test the
buffered flag. In the case of LongTasks, it tests that the flag does not
work.
Bug: 969123
Change-Id: Ie96797c4560d29c8fd537fea2025ee59f49a73da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1703591
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679091}
--
wpt-commits: c3483214b956bd3460c1d657be1172a57a9a38f8
wpt-pr: 17850
Automatic update from web-platform-tests
Use ahem.css in css-grid tests. (#17743)
* Add ahem.css to css-grid tests that regressed.
--
wpt-commits: a1aa04fe332e508c74ed02d095056b94ad91d8a6
wpt-pr: 17743
Automatic update from web-platform-tests
[scroll-snap] Improve/fix root propagation test
Note that the tests still fails in Chrome but that is going to be addressed
with a follow up CL that fixes propagation logic [1].
## General
- Move clean up logic to its own functional and declare it using "add_cleanup".
This way there is no need to assume ordering of test also clean up always run
even if test fails.
- Tests were using "start end" when only end is used. This is not needed and
confusing so changed to "none end" to make this clear.
- Use 800 as destination for scroll to not confuse it with 1000 which is the
target position.
## Test 1
At this point body's writing-mode is still the default value i.e.
`horizontal-tb`. So inline axis is still "horizontal". This means that
`scroll-snap-type: inline mandatory` snaps horizontally. But the test
expected it to snap vertically which is not correct!
Fix: We should actually avoid depending on writing-mode in this test as it
keeps the test more focused on the actual thing that is being tests and also
avoids the problem. So use "y mandatory" instead.
## Test 2
Added a check to this test to verify behavior on the non-snapping axis.
Also added a new test to check horizontal-tb which was present in some
from in the original test.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1704859
Change-Id: I330fb02ef4d81c82c5371bf608c1930568fb1dc8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696190
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679086}
--
wpt-commits: e639e4acb2728c76acc5c9cebcf09b256f211984
wpt-pr: 17865