Automatic update from web-platform-tests
Use testdriver Action API to automate wpt tests with two touch fingers
Use testdriver Action API to automate wpt tests with two touch fingers,
pointerevent_touch-action_two-finger_interaction.html.
Bug: 606367
Change-Id: Ia5a0977b3bda9c506dae99c7bfe500fe2a887cad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1839017
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703867}
--
wpt-commits: 583fb12c61bca2dfd94ba12469d0c1a97f6883a4
wpt-pr: 19522
Automatic update from web-platform-tests
[LayoutNG] Fix font-orientation segmentation
When there are no script segments (i.e., all the text is in
single script) and in vertical flow, we create a single
segment and split it at the font-orientation boundaries.
This patch fixes to create the single segment from the first
text item, not from the first item. If it is created from the
first item and the first item is not a text item, we may give
incorrect script and/or font-orientation to HarfBuzz.
Bug: 1006154
Change-Id: I5ea87920f8cbc76cdc13fe25611f7a7a34284813
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847697
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703803}
--
wpt-commits: 4cd56bbc0f6a79a08342e35cbbcfb7e9b700214e
wpt-pr: 19574
Automatic update from web-platform-tests
Change key from "Ctrl" to "Shift" in actionsWithKeyPressed.html
In this test, we want to test that testdriver Action API supports key
and mouse action interactions. Clicking with "Ctrl" key pressed on Mac
causes a context menu open, which fails itself and prevents a
subsequent test from running. We can use other keys such as "Shift"
or "Alt", which do not open any context menu.
Change-Id: Id9b48440306eeddbd97114bc1ac0f4c9c3c012fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845994
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703792}
--
wpt-commits: de83b0a0759656d93b536457791bb601c5b7424a
wpt-pr: 19555
Automatic update from web-platform-tests
Add some tests for triggering SMIL events via syncbases
Tests a new begin/end being added by a syncbase, and the corresponding
'end' event being fired.
Bug: 998526
Change-Id: Ie40f196d4ef2c5fb6b65fced80890a965415cace
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1840692
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703778}
--
wpt-commits: ef62c8fa7b2078d3cbe0e2364573b6e00a72f7d2
wpt-pr: 19511
Automatic update from web-platform-tests
[Native File System] getFile() returns a File sized correctly
The getFile() method on NativeFileSystemFileHandleImpl returned a File
that wasn't sized correctly. This caused issues when trying to use
methods on the File object that would use the bounds to do operations.
BUG=1011179
Change-Id: If900ac39be6b7bfc9d693680aa5d20b6b9c926d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845998
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703764}
--
wpt-commits: eb2527b61be8bfcf0916faa56c47624c90d32bd2
wpt-pr: 19553
Automatic update from web-platform-tests
[LayoutNG] Fix line breaking when `font-size: 0`
This patch fixes line breaking when break opportunities have
`font-size: 0`.
`font-size: 0` makes all characters at position 0. This
confuses when |NGLineBreaker| needs to rewind, and tries to
find the break opportunity before the current one.
This patch fixes it by using |PreviousBreakOpportunity| in
such case.
Bug: 1006127
Change-Id: I449d6f8aaba4deccd458c5e077920b1a8bf79305
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1843991
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703753}
--
wpt-commits: 7fbe6fe5fe834bf28d9171bf92d90287186020e8
wpt-pr: 19541
Automatic update from web-platform-tests
Update mypy from 0.720 to 0.730
--
fixup! Update mypy from 0.720 to 0.730
--
wpt-commits: d7789eace2c576625633a913cf5f835aae68238e, 3982e1b6a11e163be4469598421b0cbcf6ecab82
wpt-pr: 19327
Automatic update from web-platform-tests
[GitHub Actions] shorten names of workflow files and names
With this, instead of checks named like this:
- "Build & Release Manifest / manifest-build-and-tag"
- "Build & Publish Documentation Website / website-build-and-publish"
The checks will installed be named like this:
- "manifest / build-and-tag"
- "documentation / build-and-publish"
--
wpt-commits: ff3e2b5734b8ec13fe2f8b9aff138c5578f373f8
wpt-pr: 19567
Automatic update from web-platform-tests
Use `zstd --no-progress` in manifest_build.py (#19568)
gzip and bzip2 are silent by default.
--
wpt-commits: 1dd29f0138509c085c01df7ec3214231d28853b8
wpt-pr: 19568
Automatic update from web-platform-tests
The size of OverflowClipRect is negative
When scrollbar wider than the scrollar, the size of OverflowClipRect
is negative which will affect the value of scroll offset. This patch
make the size non-negative.
Bug: 987566
Change-Id: I7fa80e4a17bc48303713a1a191230d0b3e7d0dd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1840492
Commit-Queue: cathie chen <cathiechen@igalia.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703662}
--
wpt-commits: 6e56893172d7f8bc833e9859c97ad5e52e9eb937
wpt-pr: 19566
Automatic update from web-platform-tests
Turn on backpressure for blink::WebSocketStream sooner
Apply backpressure to blink::WebSocketChannel before the WebSocketStream
handshake starts, rather than after it completes. This avoids a race
condition where more of the first message is read than should be.
Also fix flakiness in the
external/wpt/websockets/stream-tentative/backpressure-receive.any.js by
doubling the size of message used.
BUG=1002780
Change-Id: I915c71a4b81b95375b7c4c584f7782d5336cba85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844911
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703610}
--
wpt-commits: b3807b6ffe70db1bcaa28cf8b5aa8c6da025b5fa
wpt-pr: 19563
Automatic update from web-platform-tests
Worklet: Reject addModule() with script's error to rethrow if available
This CL makes Worklet#addModule() fail with a more specific error object
compared to before.
Before this change, Worklet::addModule() was rejected with AbortError regardless
of an actual error reason, and that made it difficult for developers to debug
worklets. This behavior was defined in the Worklets spec, but it was changed
recently (see the links below).
After this change, Worklet::addModule() is rejected with script's error to
rethrow when it is available as the new spec defines.
Spec changes:
- https://github.com/w3c/css-houdini-drafts/pull/958
- https://github.com/w3c/css-houdini-drafts/pull/967
Chromestatus:
- https://www.chromestatus.com/feature/5116796497559552
Bug: 782066
Change-Id: Iabd30eff28ed1bffed9219898649a89b8abebbb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1258785
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703606}
--
wpt-commits: 162858b9961ab26dbbe27e07bea2d6e6d10702df
wpt-pr: 19462
Automatic update from web-platform-tests
Ensure image cache keys on element CORS status.
--
wpt-commits: 62ee04cd0ea0765975f82fb1b130990df9ecf8e3
wpt-pr: 19529
Automatic update from web-platform-tests
CSS: Test shorthand expansion
When a longhand value is omitted, the longhand should have the specific
initial value for the shorthand, not 'initial'.
Bug: 501673, 772772
Change-Id: I0986013e6785852861b79926dd0696314c758ff7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1839934
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703528}
--
wpt-commits: bb904ca75f9da8d5392b4ed670f8033ecfd361f3
wpt-pr: 19509
Automatic update from web-platform-tests
docs: update the readme link for running https tests (#19551)
--
wpt-commits: f951c9d8c79e03d656d2427fa5f3e0dce4c6efe5
wpt-pr: 19551
Automatic update from web-platform-tests
Clear-Site-Data: clients uncontrolled by service workers after storage directive (#19132)
Adds a failing test, asserting that pages actively controlled by a service worker become uncontrolled after the Clear-Site-Data storage directive.
We agreed on this behavior in a spec issue and confirmed the need for this test at the TPAC Service Workers F2F.
https://github.com/w3c/ServiceWorker/issues/614
F2F notes: https://docs.google.com/document/d/1_Qfw5m3BJEaL1xIzTJd41HXjgJ9gq7mroBDXqSJIzic/edit
--
wpt-commits: 8be01b6e0d191a641f45ad59e83718155775921d
wpt-pr: 19132
Automatic update from web-platform-tests
[web-animations-1] Fix typo in test (#19554)
--
wpt-commits: d9a9f2970d628001ff100548a6fd1ee750802893
wpt-pr: 19554
Automatic update from web-platform-tests
[docs] Add documentation for common/
Part of #17913.
--
wpt-commits: 2ae499f937640068f33d547423bfeb8c3dbf5295
wpt-pr: 19548
Automatic update from web-platform-tests
[testharness.js] Implement `single_test` option (#19449)
The behavior and deployment schedule of this option was defined via the
following web-platform-tests RFC:
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
--
wpt-commits: 819a234d3dd3a8400d57fa449123cbb01bb33226
wpt-pr: 19449
Automatic update from web-platform-tests
Initial implementation of performance.measureMemory API
This adds IDL files and an experimental feature flag for the API.
The implementation simply forwards to v8::Isolate::MeasureMemory.
Bug: 973627
Change-Id: I80ac8b78e81a6fad6b25370b419a0392f6589cee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1796364
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703262}
--
wpt-commits: 019a83d93404f649f226f8e49cdb768115912a4f
wpt-pr: 19258
Automatic update from web-platform-tests
[WPT/referrer-policy] Add worker subresource tests
This CL adds tests of subresources sent from worker global scope,
including XHR/Fetch API inside workers and nested workers.
The tests are failing on Safari and Firefox, largely because
of differences of referrer policy inheritance rule
(which is a spec-level issue).
Bug: 906850
Change-Id: Ia385d72918df5d4318c7fc58306bfc614a3bd4b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1785499
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#702280}
--
wpt-commits: 28cbc22e946b0a481435ab299490b810b2ec29c8
wpt-pr: 18854
Automatic update from web-platform-tests
DecompressionStream: Accept BufferSource chunks
The previous version of DecompressionStream accepted only Uint8Array
as its input, so I added change to accept ArrayBuffer and
other ArrayBufferView like Int16Array.
I also added a test.
Bug: 999091
Change-Id: I8c153c3f639cb4e9b8563128e4cce1e6c6597cb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1831920
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Canon Mukai <canonmukai@google.com>
Cr-Commit-Position: refs/heads/master@{#703221}
--
wpt-commits: eb07ced561d725de35e072dcae68f49e6d61b37a
wpt-pr: 19427
Automatic update from web-platform-tests
Fix shadow-dom/focus/focus-selector-delegatesFocus.html for slotted elements
As specified in https://html.spec.whatwg.org/multipage/semantics-other.html#element-has-the-focus,
an element has focus when itself is in the focus chain or its shadow root contains the focused element.
Since the shadow tree does not contain a slotted element, its shadow host should not match :focus pseudo class.
Otherwise, the shadow host's tree would end up containing more than one element which match :focus,
for example, the shadow host and its direct child which is actually focused.
--
wpt-commits: 080acb0967ec06504808de9a25f64290df3d6128
wpt-pr: 19530
Automatic update from web-platform-tests
css-flexbox: fixes for -webkit-box using LayoutFlexibleBox
This addresses two problems that triggered CHECKs/use-after-free:
LayoutBlock, for -webkit-box, needs to add children to anonymous
blocks in some cases.
LayoutFlexibleBox should not merge anonymous flex items for
-webkit-box.
BUG=1010706
TEST=none
Change-Id: Ic8cb22f4f031813c1e1447bc23f4bfb930b3caec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838754
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703115}
--
wpt-commits: 6c1b9ea175aface98eef5e8851b75a00d0a1ba72
wpt-pr: 19528
Automatic update from web-platform-tests
WebXR: experimental DOM Overlay support for immersive-ar mode
This opt-in mode keeps DOM content visible as a transparent overlay while
in an immersive-ar WebXR session. It is activated by requesting an optional
or required feature on session start:
navigator.xr.requestSession(
'immersive-ar',
{optionalFeatures: ['dom-overlay-for-handheld-ar']});
This functionality is only available if the corresponding feature flag
chrome://flags#webxr-ar-dom-overlay is enabled.
On session start, this fullscreens the <body> element. The application can
use the Fullscreen API to change the visible element. Exiting the session ends
fullscreen mode, and calling document.exitFullscreen() exits the immersive-ar
session if there are no remaining fullscreened elements.
(As of this CL, changing the fullscreen element doesn't fully update layer
visibility, so non-fullscreen content can remain visible unexpectedly.
That's being addressed in a followup.)
Change-Id: I77b767b111436b45e2b584e46a390a68473ab118
Bug: 991747
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1741008
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703074}
--
wpt-commits: 585aa49b4085875142e37fb10398c2d3dee122f9
wpt-pr: 19013