Automatic update from web-platform-tests
Use testdriver Action API in WPT pointerevent tests - Part 10
In order to run the web-platform-tests automatically, we will use
testdriver Action API in all the wpt to simulate inputs. Here we are
changing some pointerevent input test which taps on the elements inside
an inner frame.
This is the tenth CL that changes part of the pointerevent input
tests.
Bug: 606367
Change-Id: Ib90c92e8267f17fed74a86d70ca6d739b5ccedb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638914
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#675891}
--
wpt-commits: e6fff725295afce26b2000ab7644a69d29f78c08
wpt-pr: 17789
Automatic update from web-platform-tests
webdriver: allow trailing slashes for navigate_to WPT test (#17805)
The handling of file:// URLs is implementation defined.
--
wpt-commits: 43a2ddb71497ee04157fe6fc8ce29d7e4ef2b6ec
wpt-pr: 17805
Automatic update from web-platform-tests
LazyLoad: Add external web platform tests for the "loading" attribute.
This CL includes tests for:
- Testing that images and iframes with the attribute loading="lazy" are
deferred until they come into view
- Testing that images and iframes with the attribute loading="eager" are
loaded immediately
Bug: 916260
Change-Id: I323faa31c7683663d0d0136a719cf83c25758ad6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1417117
Commit-Queue: Dominic Farolino <dom@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676804}
--
wpt-commits: 9919d0f04266001686c09d47ff6e25c98b48d91f
wpt-pr: 14914
Automatic update from web-platform-tests
[cssom] getComputedStyle not getComputedValue (#17799)
Fix typo in test titles.
--
wpt-commits: 9daa6ffd6eb28afb0940b7ac304b08e8383fc527
wpt-pr: 17799
Automatic update from web-platform-tests
CSS property 'tab-size' should take 'number' instead of 'integer'.
According to https://drafts.csswg.org/css-text-3/#tab-size-property,
let 'tab-size' take css 'number' value, not css 'integer' value.
Bug: 974090
Change-Id: Idb235eacde59f5bae1ab7fb814425fae4b93a227
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1689165
Commit-Queue: Joonghun Park <pjh0718@gmail.com>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676741}
--
wpt-commits: 01669b3a69c55c077a6f5212c295528c89388d6c
wpt-pr: 17779
Automatic update from web-platform-tests
[compositing] Computed value tests (#15319)
background-blend-mode, isolation, mix-blend-mode computed values are as specified.
https://drafts.fxtf.org/compositing-1/#property-index
All tests pass with Firefox.
Three background-blend-mode tests fail with Blink/Edge/Safari:
expected "normal, luminosity" but got "normal"
expected "screen, overlay" but got "screen"
expected "color, saturation" but got "color"
--
wpt-commits: d0a227ec363d652a133d53bdda7ab2ef976e6008
wpt-pr: 15319
Automatic update from web-platform-tests
[docs] Normalize spelling of "test suite"
The documentation uses the terms "testsuite" and "test suite"
interchangeably. Normalize on "test suite."
--
wpt-commits: 03fcaec457809e26a282727951c155b82660e159
wpt-pr: 17797
Automatic update from web-platform-tests
[docs] Expand landing page
Currently, the documentation website's landing page contains only a
table of contents. The introductory material is accessible through the
first link in that index.
Because the landing page is itself an introduction, it ought to offer
some explanation of the project's purpose and structure.
Re-use the introductory text found in the project's README.md file since
this is slightly more complete than the corresponding text in the
"introduction" page. Move other high-level information to the landing
page and rename the "introduction" to "testsuite design" in order to
better describe its more narrow focus.
--
[docs] Correct typos
--
wpt-commits: f3cdfbcb428ca2f711d0b5128264d3f7cfcfd187, 6d60c3d31206401a3e22db74c68429a302443d9f
wpt-pr: 17634
Automatic update from web-platform-tests
Fix WPT manifest updates when within a git tree
This has been broken since bug 1545629 landed, when we started using
git to (quickly) get hashes of unchanged files. Unfortunately, the
logic for finding changed files only worked when the test root was the
root of the git repository.
Differential Revision: https://phabricator.services.mozilla.com/D34702
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1558363
gecko-commit: b975b4c1dfaebedabc4a09296b90303c7d5381e3
gecko-integration-branch: central
gecko-reviewers: jgraham
--
wpt-commits: 3fb0150bb0a53b5a6630e8eda7f43bf75d8a6bbe
wpt-pr: 17785
Automatic update from web-platform-tests
Move movementX/Y calculation for aura pointer-locked state to Blink. (#17295)
This change moves movementX/Y calculation for aura pointer-locked
state to Blink.
On aura, pointer lock use "move to center" to make cursor stays in
the window. With the calculation done in blink side, the move to
center event is marked as synthesize move, so that we can update
the blink side states and do not dispatch the event.
The change is under content feature flag kConsolidatedMovementXY
Bug: 802067
Change-Id: I05360dadd18a2f41481a0de9ef78a05199493857
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618306
Commit-Queue: Ella Ge <eirage@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#674237}
--
wpt-commits: 293143370ddaa9ceaee4294c78a17d97e7bdd5c6
wpt-pr: 17295
Automatic update from web-platform-tests
[UserTimingL3] Fix crash: create mark in worker
Currently, the renderer crashes when creating mark entry in worker.
The crash is because PerformanceMark::Create() return nullptr without
setting exception_state. The caller of the function assumes that
no exception indicates the PerformanceMark entry exists. Thus, when the
entry is visited, the crash occurs.
There is another bug hidden in this issue. Currently, when
window-performance is not found, Create() returns nullptr directly. It
should instead also check whether worker-performance exist.
This CL fix these issues.
To verify the change, the CL also changes the related web tests from
*.html to *.any.js, which enables these tests in worker's context.
Bug: 981982
Change-Id: Ia20ce1c194e4db2810ff3f1c52070e5970951600
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696085
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676484}
--
wpt-commits: 133323811602dd4ceced46f11aabb645a3582983
wpt-pr: 17773
Automatic update from web-platform-tests
Create toast action setter
Additionally, this CL adds support for passing Elements
as action in showToast, using the action setter.
This change is the latest in a series of changes implementing
new behavior added to the toast explainer in PR #43https://github.com/jackbsteinberg/std-toast/pull/43.
Bug: 972945
Change-Id: I46004883cb3b794981029aa02369918dd0077391
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1686786
Commit-Queue: Jack Steinberg <jacksteinberg@chromium.org>
Reviewed-by: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676482}
--
wpt-commits: 11051ca7a0270ae8fe07939d35cd923e5b542748
wpt-pr: 17780
Automatic update from web-platform-tests
Partially fix calc() length unit handling in media queries
When a calc() length is passed to media queries, the current code
assumes that there's always a DoubleValue(), and the unit type matches
TypeWithCalcResolved(), which is incorrect.
This patch partially fixes the issue when the calc expression can be
resolved without type conversion. Handling type conversion is more
complicated and hence left broken by this patch (as it's already broken).
Bug: 982542
Change-Id: I258b3d1aeec69fb65fbadd86981e97974239289b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696191
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676452}
--
wpt-commits: 14acac099af003b048229966651d558f508e2b9a
wpt-pr: 17775
Automatic update from web-platform-tests
custom-elements: Fix 'capture' attribute existence check in reactions/HTMLInputElement.html
Do not call 'capture' property getter.
--
wpt-commits: 40ef441b2f6ff803248bf71f03334b1326371c2b
wpt-pr: 17781
Automatic update from web-platform-tests
[css-transforms] Avoid using assert_own_property on style property. (#17778)
These `assert_own_property` tests cause these CSS tests to fail on Firefox
only, and I think these properties are not supposted to be own properties,
so use a similar way as https://github.com/web-platform-tests/wpt/pull/16892,
to test the existence of these properties.
--
wpt-commits: 47543ee66eb535b6910292f199f3b789bec263f0
wpt-pr: 17778
Automatic update from web-platform-tests
webdriver: make height and width of tests larger than min for chrome (#17772)
--
wpt-commits: 36acf7a01cb8ffbbafbd578229c5ad3fde2e47cc
wpt-pr: 17772
Automatic update from web-platform-tests
[UserTimingL3] Throw TypeError on negative time stamp
According to the spec (https://w3c.github.io/user-timing/):
1. "If markOptions's startTime is negative, throw a TypeError.",
2. "If mark is negative, throw a TypeError." when "Convert a mark to a timestamp"
The CL is to add these two checks accordingly.
Bug: 953865
Change-Id: I8475870cc883dc8c3d3d4f3e65a9d5a0a2189a58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691871
Reviewed-by: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676266}
--
wpt-commits: a819c8a4b2760a1547e63d57e39e3f34dbc5da41
wpt-pr: 17736
Automatic update from web-platform-tests
[LayoutNG] Consider inline-level OOF-positioned nodes as "adjoining".
"adjoining" objects are used to indicate that a particular node might
need relayout once its BFC block-offset is resolved. Previously we
thought that we just needed to know about "adjoining-floats".
However inline-level OOF-positioned nodes also needs to know its BFC
block-offset as the static-position of these nodes depend on where
floats are.
Previously as we didn't know that we needed to relayout these nodes
we'd get the incorrect static-position. Now these nodes get the
correct static-position.
Bug: 982403, 980908
Change-Id: I89f18298fd7379358a681b98514891d8d35bc38e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692627
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676263}
--
wpt-commits: 4f954c15e1dc8cf94f7a2231f648fb640509d9d4
wpt-pr: 17782
Automatic update from web-platform-tests
Add FakeXRDevice.disconnect method and test
Also simplifies events_deviceconnect, though because that tests behavior
that doesn't appear to be specced, that test is left internal.
Bug: 979316
Change-Id: I55cdb925aac9c2317d0a2b9f44f8eb368048aa5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1693775
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676258}
--
wpt-commits: c58628cd58109b1caa9cfd72e794929a65ee849b
wpt-pr: 17750
Automatic update from web-platform-tests
CSS: font-family initial value unspecified
https://drafts.csswg.org/css-fonts-4/#font-family-prop
Initial: depends on user agent
We can't simply have "times new roman"
in our test expectations, as Mac 10.10 .. 10.12 have
Times instead.
Bug: 966249
Change-Id: I091924585e05b2b085ab420ac553233f7346e79d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1695581
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676242}
--
wpt-commits: 037a9292ea1ffbcd4a26612e3a615a45dcbb263f
wpt-pr: 17755
Automatic update from web-platform-tests
CSS: Parsing tests for align-* and justify-* properties
Check that CSS Alignment properties accept only the values permitted
by the spec
https://drafts.csswg.org/css-align-3/#property-index
Change-Id: I93b00ac2280ca4991c24b3ee35a17047e165b8a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1694928
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676203}
--
wpt-commits: 9234a033ce9a341afec6574ddc0f2ec13c9dd35f
wpt-pr: 17756
Automatic update from web-platform-tests
Add action option string to be passed to toast showToast()
This partially implements the action option for showToast(),
as outlined in the explainer at
32237007b0/README.md (showtoastmessage-options).
For now it only handles the string or undefined cases;
the Element case will be handled in a follow-up CL once the action setter is implemented.
BUG=972945
Change-Id: I82556801a6586c89cd506669f935488e049c47c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1684466
Commit-Queue: Jack Steinberg <jacksteinberg@chromium.org>
Reviewed-by: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676168}
--
wpt-commits: 996e93b6478d485eb5867e3a5570ad88f63f878e
wpt-pr: 17774
Automatic update from web-platform-tests
[FractionalScroll] Fix web tests
This CL fixes Blink web tests so that they pass when the Fractional
Scroll Offsets flag is enabled. This flag enables fractional offsets on
the Blink main thread which breaks some tests because they assume that
offsets will be floored.
I've modernized two tests:
fast/events/platform-wheelevent-paging-y-in-non-scrolling-div.html
fast/events/scale-and-scroll-div.html
The first appears to have been an issue with js-test modifying the page
while the second was passing but the PASS string in the -exected.txt
had changed to include the factional. Both tests now pass with and
without the feature enabled.
I removed fast/events/touch/gesture/touch-gesture-scroll-div-scaled.html
since it was testing the same thing as scale-and-scroll-div.html.
The rest of the tests required changing the layout such that it doesn't
cause us to land on fractional offsets (and thus the behavior will be
unchanged with and without the flag). Where this was difficult I just
allowed for approximate equality.
Bug: 414283
Change-Id: Ie03fa06b100fb9946675e921357c1eaebfe6a37e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1690293
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676118}
--
wpt-commits: e93818b7c65d3bb3152ed5f7bf1f06019bd295bb
wpt-pr: 17671
Automatic update from web-platform-tests
[css-tables] Ignore abspos tables when checking cell descendants
If a table is added dynamically as a child of a table cell, the cell
might call innerTable->HasSections() before the inner table has
calculated its sections. The cell was checking HasSections() because
cells change sizing behavior when they have a table with sections as an
immediate descendant.
This only happened in a very narrow scenario -- when an abspos table
with a %height that does not resolve as auto is dynamically added.
Bug: 977507
Change-Id: I7856291dc6508624a81e9b65af909fa8a0d8e749
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696003
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676116}
--
wpt-commits: e5601b1ba9993f618a1838dbd4b80a9d46013e66
wpt-pr: 17771
Automatic update from web-platform-tests
Update FakeXRDeviceInterface to match webxr-test-api
This updates the FakeXRDeviceInterface to support newly added methods in
the webxr-test-api:
* simulateVisibilityChange
* setBoundsGeometry
* setLocalToFloorLevelTransform
* clearLocalToFloorLevelTransform
and supports the setting of boundsCoordinates and
localToFloorLevelTransform in FakeXRDeviceInit.
The Bounds and LocalToFloorLevelTransform functions already existed on
internal tests, and as such a few of the tests that were ready were
ported to external wpts.
Note that simulateInputSourceConnection and disconnect will be
implemented by future work.
Bug: 979316
Change-Id: Idfb8bb631bfc1f1cb13b571a90b1a41b4a6fe518
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1692038
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676087}
--
wpt-commits: a24d86919d18a817e8449357dfa6db78fe3afe93
wpt-pr: 17740
Automatic update from web-platform-tests
Fetch: Delay buffering Response data.
When a service worker executes code like `evt.respondWith(fetch(r))` we
should be able to directly pass the fetch's resulting mojo::DataPipe
through without any data copying. This previously did not work,
however, since the BufferingBytesConsumer would immediately start
buffering the Response body data.
This CL fixes this issue by delaying the start of the buffering by a
short amount of time. This gives the service worker time to drain the
pipe.
The delay is currently disabled by default behind the
"BufferingBytesConsumerDelay" feature.
Based on yhirano's draft CL at crrev.com/c/1383755.
Bug: 911036
Change-Id: I65675ce62a7ce593c8994b3e1258634840ba6c2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1679669
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676053}
--
wpt-commits: c8de5e13ed52cdf9fdee9f508e90d0ee9a09cc6a
wpt-pr: 17745
Automatic update from web-platform-tests
Add support for overscroll-behavior logical longhands
Flow relative longhands have been added to overscroll-behavior
specification [1]. This CL implements the relevant css parsing
and matching tests.
minor change: collapse all overscrollBehavior related case
statements in parser fast path.
intent-to-ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/V86fOkIaEQA/JydSaafqBwAJ
[1] https://drafts.csswg.org/css-overscroll-behavior-1/#overscroll-behavior-longhands-logical
TESTS: wpt/css/css-overscroll-behavior/ovescroll-behavior-logical.html, wpt/css/css-overscroll-behavior/parsing/*
Bug: 833953
Change-Id: I5ceefa0afb1913472c0e134b2ec07405154abfae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614026
Reviewed-by: Rick Byers <rbyers@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Auto-Submit: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676042}
--
wpt-commits: 56df7802935322e54c1ba7853963d7eb16ca0fc2
wpt-pr: 16890
Automatic update from web-platform-tests
part 2. Fix parsing of margin attributes on <body> match the spec.
The various margin attributes on <body> are "pixel length attributes" in the
spec, which should get parsed as non-negative integers. That said, Chrome and
Safari implement marginwidth, marginheight, marginleft, and margintop as
"dimension attributes" instead, and don't implement marginright and marginbottom
at all.
Differential Revision: https://phabricator.services.mozilla.com/D36372
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1562257
gecko-commit: 399e8e089eda6d6cba06bb37c3aadacc607fe6b6
gecko-integration-branch: central
gecko-reviewers: mccr8
--
part 3. Change the dimension attribute reflection test to handle the attribute name and CSS property name not matching.
We're going to need that for hspace/vspace
Differential Revision: https://phabricator.services.mozilla.com/D36373
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1562257
gecko-commit: 651433227fdbeb4fd53d90c15fac3dad3b1245a6
gecko-integration-branch: central
gecko-reviewers: mccr8
--
part 4. Fix style mapping of hspace and vspace attributes to match the spec.
Per spec, "hspace" and "vspace" are parsed as dimension attributes and are
supported on the following elements: embed, iframe, img, object,
<input type="image">, marquee. Except no one implements this for iframe.
https://github.com/whatwg/html/issues/4742 tracks the spec changing accordingly.
As far as hspace/vpace on <table> go, Safari supports them in both quirks and
standards mode, while Chrome doesn't support them in either mode. The HTML spec
doesn't have them supported at all, and neither does the quirks mode spec, so
I'm removing the quirks-only support we had to align with the specs and Chrome.
Differential Revision: https://phabricator.services.mozilla.com/D36375
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1562257
gecko-commit: bd2a2e91e9eefc6f27621620e11b93ffd8eca2e6
gecko-integration-branch: central
gecko-reviewers: mccr8
--
part 5. Fix style mapping of border attribues to more closely match the spec.
Per spec, "border" is parsed as a non-negative integer, only mapped if nonzero
(though this is not observably different from mapping even if 0, except if user
or UA stylesheets style the border), and supported on img, object,
<input type="image">, but NOT embed, iframe, or marquee.
This matches the Chrome and Safari behavior, as far as I can tell. The
substantive change here is that we are removing mapping for the <embed border>
case.
Differential Revision: https://phabricator.services.mozilla.com/D36376
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1562257
gecko-commit: b8938b6afa9c4b498ec016d1b3d50be0e50684c0
gecko-integration-branch: central
gecko-reviewers: mccr8
--
wpt-commits: 16d86b2b8c5e8cda1bb529b053af153c3b3d6887, c3dec041a318c9af716aac3b2d95ff42aa5325f9, 008153ffff00b8201548b7f420c155f23b549ee4, e0a9e5eec6d3aeb770e65ab30ee6d19824928256
wpt-pr: 17758
Automatic update from web-platform-tests
HTML: remove nonsense JSON resources
Pretty sure we don't have a use for these.
--
remove more JSON
--
wpt-commits: 84ee83638741a79a2b6cf7e67bca1f9c9dc92695, 0f05ba74bb119f32981027aa72d2e3d67e03a4c4
wpt-pr: 17574
Automatic update from web-platform-tests
webdriver: allow trailing slash in test_get_current_url_file_protocol (#17679)
Fetcing file:// protocol is not standardised which means the test
has to be more forgiving of the URL returned.
--
wpt-commits: 59ea78a393b5c69fb01d67b7267444d334082299
wpt-pr: 17679
Automatic update from web-platform-tests
HTML: cleanup [[CanBlock]] tests
(These do not require COOP/COEP treatment as they test SharedArrayBuffer on a single thread, but still seems nice to reduce clutter.)
--
wpt-commits: e4b8a06127ec937a5a57f6f96470aabb6f8d4629
wpt-pr: 17688
Automatic update from web-platform-tests
Add structured clone tests for errors
This is tests for spec changes.
- https://github.com/whatwg/html/pull/4665
- https://github.com/heycam/webidl/pull/732
--
Add tests for cloning from another realm
--
Test some stuff before cloning
--
wpt-commits: 1b4fbe0c7049d89fd805dc157f68d82616f5d203, efc79eef01ffa65273ff01736d989ff5fa79f18d, 84af6c875d378944b39d895acdcfc170736b2d3d
wpt-pr: 17095
Automatic update from web-platform-tests
Fix regression in webdriver tests
A large number of tests in webdriver directory are currently failing,
due to a change in the parameters of Find.css method by PR #17260,
which broke any tests that still supply the old parameters.
This commit changes the parameter order and uses default parameter value
to make the parameter list compatible with the old one.
--
wpt-commits: d528abff035d6596f68f21a9510ee1c5b58a1e48
wpt-pr: 17754
Automatic update from web-platform-tests
[docs] Correct typo in example of user styles
`userstyle` and `nouserstyle` are referenced as CSS class names in this
document, so they should be declared as such.
--
wpt-commits: 0e95bf3183c7358f3bb428f6f1cc3db5e86b1e79
wpt-pr: 17748
Automatic update from web-platform-tests
[docs] Remove unused files
These files have not been used since the documentation site was
re-implemented to use Sphinx. They may be removed without affecting the
published website.
--
wpt-commits: 699d35e4e53a7f4595a43b43bcc96c21e29a80e9
wpt-pr: 17739
Automatic update from web-platform-tests
Orientation/Portals: make SharedArrayBuffer non-optional (#17720)
The plan is that SharedArrayBuffer is always available.
--
wpt-commits: bb674f5baec1f1b25d8da1a6fe3d941c3b106e9a
wpt-pr: 17720
Automatic update from web-platform-tests
[UserTimingL3] {}, null, undefined passed to start treated as 0
According to the spec (https://w3c.github.io/user-timing/#measure-method),
UserTimingL3 API has the second argument being:
optional (DOMString or PerformanceMeasureOptions) startOrMeasureOptions
This indicates that the arg cannot distinguish between:
1. null
2. {}
3. undefined
4. { invalidDictProperty }
According to the spec:
3.1.3 measure() method...
3. Compute start time as follows..
4. Otherwise, let start time be 0.
When these indistinguishable values are passed, they should be
interpreted as start time being 0.
Bug: 953840
Change-Id: I052a7823d9ae8b27056f53f04a26fcc93421db75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691862
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#675873}
--
wpt-commits: 1f346b050d87656a040fa4fdf9f99567164e2a2b
wpt-pr: 17735
Automatic update from web-platform-tests
Handle non-negativeness of blur radius properly
Spec on blur radius says [1]:
"... Specifies the blur radius. Negative values are not allowed."
Current implementation performs parse time range check, which is
incorrect as calc() doesn't always have a double value. And spec
requires clamping instead of parse time check for calc() [2]:
"Parse-time range-checking of values is not performed within math
functions, and therefore out-of-range values do not cause the
declaration to become invalid. However, the value resulting from
an expression must be clamped to the range allowed in the target
context."
This patch changes it to pass |kValueRangeNonNegative| to
|ConsumeLength| as it handles non-negative calc() more properly.
This is also preparation for adding DCHECK into GetDoubleValue() to
avoid calling it on calc() without a double value.
[1] https://drafts.csswg.org/css-backgrounds-3/#shadow-blur-radius
[2] https://drafts.csswg.org/css-values-4/#calc-range
Bug: 979895
Change-Id: Ia8c36641f4ec4111ecf5a94a6ffc6eaacf22049c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691747
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#675815}
--
wpt-commits: 65d3f17c56ea812d121669e6268a0cec4a4ea4a6
wpt-pr: 17741
Automatic update from web-platform-tests
Serialization of consecutive tokens. (#17746)
* Serialization of consecutive tokens.
Per <https://drafts.csswg.org/css-syntax/#serialization>, many token pairs, if they find themselves consecutive in a value, must be serialized with a comment between them, because otherwise upon serialization+reparse they'll produce a different token stream.
--
wpt-commits: dacb51937397fd06727727614e255f223e7cb9f3
wpt-pr: 17746
Automatic update from web-platform-tests
Add new tests for Core-AAM: (#17742)
* aria-expanded on: application, checkbox, switch
* aria-required on: checkbox
* aria-posinset and aria-setsize on: row
* inclusion of children of math role
* group as valid child of listbox
* menucheckbox as valid child of group in menu
* subscript and superscript roles
* meter role
* time role
* insertion and deletion roles
--
wpt-commits: f56d498d4dde12aacf8d6bbe591d35488af06a2b
wpt-pr: 17742
Lan Wei
julianrkung
rajendrant
Eric Willigers
Joonghun Park
Mike Pennisi
L. David Baron
moz-wptsync-bot
Blink WPT Bot
Liquan(Max) Gu
Jack Steinberg
Xiaocheng Hu
Kent Tamura
Boris
Eldar Rello
Ian Kilpatrick
Alex Cooper
Eric Willigers
Darwin Huang
David Bokan
David Grogan
Ben Kelly
Majid Valipour
Nicolás Peña Moreno
Boris Zbarsky
fergald
Anne van Kesteren
Yutaka Hirano
John Chen
Tab Atkins Jr
joanmarie