Automatic update from web-platform-tests
Remove .catch() because it turns the promise from rejected to resolved, and thus doesn't properly trigger the test scenario (#15876)
--
wpt-commits: 5519cadb33916f291885bdf42177cb30571afb50
wpt-pr: 15876
Automatic update from web-platform-tests
Add test for charLength in SpeechSynthesisEvent constructor (#15732)
Follows https://github.com/w3c/speech-api/pull/50.
--
wpt-commits: 3531dc2a994d918914e4751b97807ce8d79bf4b7
wpt-pr: 15732
Automatic update from web-platform-tests
Reland "Make pointer capture work in same origin frame"
This is a reland of d44248f2a896421c1382c1dbbf0d7e1a9b798470
Original change is reverted by findit due to test flaky.
The flaky test is:
fast/events/pointerevents/mouse-pointer-capture-in-iframe.html
This is reland with fixing tests.
Original change's description:
> Make pointer capture work in same origin frame
>
> We used to send mouse event to the subframe before apply the pointer
> capture target, and it causes the pointer capture doesn't work when
> capture to a outer frame target and move to inner frame.
>
> This CL changes three things:
> 1. 'Rename' the |capturing_mouse_events_element_| to
> |capturing_subframe_element_| as it only used for the frame capture
> (There is plan to remove the frame capture logic once we have pointer
> capture work correctly)
> 2. On HandleMouse*Event, instead of always perform a hit test, we use
> either frame capture target or pointer capture target to re-construct
> the HitTestResult.
> 3. When using the capture target, update the hover active state for
> capture target.
>
> This change makes captured pointer event sent correctly when over
> same origin frame, and also decrease the hit_test_count because of
> frame capturing.
>
> Note that after this change, we still NOT allow set/release pointer
> capture across same-origin frame as the pointer id and active statue
> is per frame.
>
> See design doc:
> https://docs.google.com/document/d/1cOZu98UuKk5bdARUQKmj2Q8YoEMpd9l78T0k-cf5ttc/
>
> This change is under a blink flag UnifiedPointerCaptureInBlink.
>
> Change-Id: I61c6a02086535d2a145df9d414df0bdc9673101e
> Bug: 936190, 919908
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1446556
> Commit-Queue: Ella Ge <eirage@chromium.org>
> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
> Reviewed-by: David Bokan <bokan@chromium.org>
> Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#640055}
Bug: 936190, 919908
Change-Id: Icc374c16b1aee0b9125593801c8787f28c7db554
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1520941
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#641316}
--
wpt-commits: a22a149b9ed01e4669089690170c243760f787bb
wpt-pr: 15817
Automatic update from web-platform-tests
Support international characters in animation worklets.
Code in cc/ is not permitted to use wtf::String. Thus, we perform conversions between wtf::String and std::string. The later is not aware of encodings. This is OK provided a consistent encoding is used for round tripping, where the encoding supports the set of allowed characters. The UTF-8 encoding is adequate for this task and supported by wtf::String.
Bug: 940493
Change-Id: Ie2b994412f502ea11df06713439b8cf8ffedc885
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1524087
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#641278}
--
wpt-commits: 151b78244c1595920405ca887e59c5f17f1ce6e5
wpt-pr: 15843
Automatic update from web-platform-tests
PaymentDetailsModifier.supportedMethods should be a DOMString
--
Merge pull request #15874 from danyao/danyao/payment-request
PaymentDetailsModifier.supportedMethods should be a DOMString
--
wpt-commits: f391e31524a0622cae86a2f3e3b1984333bd87be, 5cce79aacdd1c2a5dfcca6408687a84aac20b186
wpt-pr: 15874
Automatic update from web-platform-tests
Add manifest.TypeData.to_json to compute a TypeData's JSON obj (#15870)
If we're still using TypeData.json_data, we don't need to create
a new object here.
--
wpt-commits: 7cc1301eaf905c0cb5fa32b4bc9252943ecdf6f4
wpt-pr: 15870
Automatic update from web-platform-tests
Fix manifest.vcs.Git._local_changes to actually work
--
Avoid splitting too much in manifest.vcs.Git.__iter__
--
wpt-commits: 08018d794d0020bbc1d0ec41897762e41f07c6ec, 554d5946c21a7dbe7886d75727e0cf79475e6bf3
wpt-pr: 15862
Automatic update from web-platform-tests
Add a timing test for WebAssembly.instantiateStreaming.
--
wpt-commits: 60b4c15e84d9cee4f6a138793aed21dddd2a995c
wpt-pr: 15833
Automatic update from web-platform-tests
Fix c5510-padn-000-ref.xht to use same text color as test
--
Fix white-space-003.xht to use same wording as shared ref
--
Define margin for white-space-pre-element-001.xht
--
Alter margin in white-space-processing-040.xht
--
Merge pull request #15671 from gsnedders/css2-fixes
Fix a bunch of universal failures in css/CSS2
--
wpt-commits: 9a1e0b67b2f62569fc1185c869a5b01b48d1be70, f38bb3b176a1718d25ae7207f21d29a1682dddf0, 530a5b80bb6c2fb17763c32b64c6dda6201ee203, c9cc69953533a15712013c979a5cb33697d3567a, 24c8b9e1fe0cf1cb07c4314b1b6f3b15699634ef
wpt-pr: 15671
Automatic update from web-platform-tests
Drop item.meta_key as we only need hashes to depend on test ID
We used to rely on hash(item) changing to update the manifest; we
haven't had that (dubious) behaviour in many years now, so all this
can go.
--
fixup! Drop item.meta_key as we only need hashes to depend on test ID
--
wpt-commits: 702c8f03a81135e52341a3a288d055f086f90b6f, 96dd05afd40377e90acd1da0599846be65fa8001
wpt-pr: 15842
Automatic update from web-platform-tests
Add one test for "Update the Rendering" section of HTML. (#15510)
I'm hoping to write a bunch of tests for this section, as part of the
investigation of w3ctag/design-reviews#72, and this is the first one.
It tests that request animation frame callbacks happen in the correct
order across multiple documents.
Gecko, Chromium, and WebKit all fail in different (and nondeterministic)
ways, although I've seen occasional passes.
--
wpt-commits: 9e96f63ccd0a6e2f5f6511ff1aa8aaaa708b494f
wpt-pr: 15510
Automatic update from web-platform-tests
Test linethickness with unitless zero
--
Merge pull request #15838 from rwlbuis/zero_unitless
Test linethickness with unitless zero
--
wpt-commits: 2ddeacbbebed05177b984798447e390efce5a824, 93d8f9c82ab0c9c954dac9432de9b93e658f7238
wpt-pr: 15838
Automatic update from web-platform-tests
[resource-timing] Add TAO null check tests and make sure they pass
This CL brings in the pending test [1] for a null TAO check and opaque
origins, adds another test to make sure only case-sensitive "null" is
taken into account, and changes the TAO implementation to actually pass
the tests.
[1] https://github.com/web-platform-tests/wpt/pull/13507
Change-Id: I1656d5a5cf2a833ada4dc83278eda0a07cec66c7
BUG=940898
Change-Id: I1656d5a5cf2a833ada4dc83278eda0a07cec66c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1517653
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#641123}
--
wpt-commits: b90e1587455350962c4efc39b7c1bbf588d6ab64
wpt-pr: 15782
Automatic update from web-platform-tests
[wake-lock] Adapted the rest tests to latest spec (#15803)
* [wake-lock] Adapted the rest tests to latest spec
- Remove wakelock-api.https.html as I believe they should be
covered by IDL tests
- Remove wakelock-cancel-twice.https.html, wakelockrequest-is-independent.https.html,
wakelock-promise.https.html as those APIs had been changed, I will add
tests for the new ones in a follow-up.
--
wpt-commits: ea2ee737f8f7e50a1ab26c98ecebe528dc0197b4
wpt-pr: 15803
Automatic update from web-platform-tests
[css-properties-values-api] Compute <length> values to px.
According to the spec, the computed value of <length> registered properties
is the absolute value expressed in pixels. Currently, we are only behaving
correctly if the value is a calc() or if the CSSPrimitiveValue contains a
relative unit (e.g. em). This means that values like '1in' would not be
expressed in pixels.
As of this CL, we absolutize any <length> which isn't already a simple
(non-calc) px value.
R=futhark@chromium.org
Bug: 641877
Change-Id: Idec079671a094952e122847fc5ebd4b0cb609674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1520586
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#640922}
--
wpt-commits: 2d68590d46a990bf28a08d6384a59962d2e56bf6
wpt-pr: 15811
moz-wptsync-bot
Danyao Wang
Tab Atkins Jr
Samuel Dallstream
Ella Ge
Kevin Ellis
Danyao Wang
Robert Ma
autofoolip
Anne van Kesteren
Sam Sneddon
Ms2ger
Tavmjong Bah
L. David Baron
Rob Buis
Yoav Weiss
Wanming Lin
kaixinjxq
Anders Hartvoll Ruud
Mustaq Ahmed