Automatic update from web-platform-testsAvoid using Promise.prototype.finally in idlharness.js
In this context, using .then() achieves the same thing because of the
preceding .catch().
Fixes https://github.com/web-platform-tests/wpt/issues/12428.
--
wpt-commits: 8b3baca3d46530aa04a12afa2fe00951800e0f2c
wpt-pr: 12432
Automatic update from web-platform-tests[Battery] Correct IDL file name (#12422)
The IDL file name is `battery-status.idl`
--
wpt-commits: 1f430df57ffa8d35f5d147bed09d769b2144b90d
wpt-pr: 12422
Automatic update from web-platform-testsTest that there's no help cursor on help links (#12415)
Follows https://github.com/whatwg/html/pull/3902.
--
wpt-commits: 619c31856b3d91ab022f908c1154aff7aa9f2bde
wpt-pr: 12415
Automatic update from web-platform-testsWeb Locks API: Update spec/explainer/idl links
Spec work has moved into the WICG repository, so update links:
Explainer: https://github.com/WICG/web-locks/
Spec: https://wicg.github.io/web-locks/
Bug: 161072
Change-Id: I450beb25d8a7c9c0a80b06b7e84d7ac8db3cece1
Reviewed-on: https://chromium-review.googlesource.com/1171213
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582356}
--
wpt-commits: 6b3194d4b26ad3c2746e2b2773805e792b1f879d
wpt-pr: 12414
Automatic update from web-platform-testsRewrite Budget API IDL test to use idl_test (#12390)
--
wpt-commits: 13f24abbc0da9d73ede59516bb6289592ff94216
wpt-pr: 12390
Automatic update from web-platform-tests[LayoutNG] Flip for writing mode when calculating inline bounding box.
LayoutInline::LinesVisualOverflowBoundingBox() is expected to return
coordinates with a logical block coordinate. So we need to flip for
writing-mode vertical-rl.
Discovered while investigating why
wpt/css/css-position/position-sticky-writing-modes.html fails. It had
some weird repaint issues (that I discovered when picking the test
apart) that this CL fixes. That's not enough to fix the test, though.
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I9a8930cc6de01991592282491677327e3406acfb
Reviewed-on: https://chromium-review.googlesource.com/1170835
Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582222}
--
wpt-commits: c960c4cf4c4849ee5207d9235bb4da7939a53d58
wpt-pr: 12412
Automatic update from web-platform-tests[Background Fetch] Reject BackgroundFetchUpdateEvent::UpdateUI if called again
Also add WPT that check
- calling updateUI works
- calling updateUI more than once throws an exception
Change-Id: I4b8e1847a09fd84a087d4f4af996ccf19c9f212b
Reviewed-on: https://chromium-review.googlesource.com/1159073
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582140}
--
wpt-commits: d6763dd2689061fb3dc5175852f56009fd3d1103
wpt-pr: 12263
Automatic update from web-platform-testsFix service worker tests generated from non-https .any.js
Note: this contains a change to the expected behaviour of test
runners.
Previously .any.js tests specifying a serviceworker variant generated
a url like foo.https.any.serviceworker.html. But that causes a problem
because that looks exctly like a url generated from a file named
foo.https.js. This ambiguity, together with the fact that wptrunner
wasn't actually looking at the https flag in the test id, but only in
the filename, meant that service worker tests weren't being run
properly.
This change stops adding .https. to serviceworker tests generated from
.any.js files and instead makes .serviceworker. in the test id
directly mean that the test should be loaded over https.
--
wpt-commits: bfec5399443c15c7a201a3d2b5505967433f570c
wpt-pr: 12381
Automatic update from web-platform-tests[LayoutNG] Propagate abspos inline container
OOF elements with inline container that were not direct descendants
of container did not have their inline container set correctly.
This caused Google SERP page to display a menu incorrectly.
Test
Bug: 867307
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Iefc78785d296c87d7fc1f34abe3980c0783d6818
Reviewed-on: https://chromium-review.googlesource.com/1165953
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582139}
--
wpt-commits: a827a82cd6be5bfca648b98904c45e2fa3777d20
wpt-pr: 12363
Automatic update from web-platform-testsDOM: fix test case which relied on outdated Name/QName production
--
wpt-commits: 848ceffad26e92d47ffe790ed8b650906b2c2343
wpt-pr: 12202
Automatic update from web-platform-testsIntroduced blink::mojom::WebUsbService with restricted methods.
This CL introduced blink::mojom::WebUsbService implemented
by WebUsbServiceImpl in chrome/browser/usb which used to be
WebDeviceManager.
Paralleling with device::mojom::UsbDeviceManager, the new interface
aims to simplify the interactions with Blink, and a meaningless
argument of GetDevices() method has been reduced in this CL.
device::mojom::UsbChooserService will be merged to this interface in
subsequent CLs.
BUG=699790
Change-Id: I891c56460425c20d2e8d067f9335091f6945ae7d
Reviewed-on: https://chromium-review.googlesource.com/1151065
Commit-Queue: Donna Wu <donna.wu@intel.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582108}
--
wpt-commits: 56d7c6101f0ae73fd87d555623dd2c608d4cfc8c
wpt-pr: 12239
Automatic update from web-platform-tests[wptrunner] Remove unused code
The file "reduce.py" is not structured for direct execution, and it does
not appear to be reference by any other file in the wptrunner project.
In addition, it includes incorrect references to the `TestLoader` and
`TestFilter` classes, and it invokes their constructors with arguments
that do not match their supported parameters.
Because no other code invokes the `wptrunner.run_tests` function with
the `test_loader` keyword argument, the associated code path may also be
removed.
--
wpt-commits: 1835be0041981df6ec0ad3d263fe5cf9aa2d6907
wpt-pr: 12367
Automatic update from web-platform-testsUpdate interfaces/*.idl boilerplate from reffy-reports (#12403)
The boilerplate has changed:
https://github.com/tidoust/reffy/pull/114
This change updates the files where *only* the boilerplate would
differ, files with other differences are left untouched.
--
wpt-commits: 9444c46e506b6231888b9b21613a8eceb4dac525
wpt-pr: 12403
Automatic update from web-platform-tests[Streams] Add a test for piping to errored (#12296)
The test 'Piping from an errored readable stream to an errored writable
stream' was misnamed, as the destination writable was erroring, not
errored. Rename it. Add a variant of the test where pipeTo() isn't
called until the destination is errored.
Split other tests for errored writables into erroring + errored versions.
--
wpt-commits: 8ab7aace6a65a045a1b8823988623afc4c1e4f09
wpt-pr: 12296
Automatic update from web-platform-tests[css-logical] Implement flow-relative values for 'float', 'clear' and 'resize' properties
They are implemented behind the CSSLogical runtime flag.
Intent to Implement:
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/48OwfwZrbvI/A1XZFGkzAwAJ
Spec: https://drafts.csswg.org/css-logical/#directional-keywords
BUG=850004
TEST=external/wpt/css/css-logical/logical-values-float-clear.html
TEST=external/wpt/css/css-logical/logical-values-resize.html
The tests still have some failures because sideways writing modes have
not been implemented yet (http://crbug.com/680331).
Change-Id: Ieede2703368a44f3ce9996e917857226795ebaea
Reviewed-on: https://chromium-review.googlesource.com/1163667
Reviewed-by: Anders Ruud <andruud@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#581904}
--
wpt-commits: 9f51afc215d4f882a7ae069494ed37ea2c9503b1
wpt-pr: 12326
Automatic update from web-platform-testsRewrite secure-contexts/idlharness.any.js to use idl_test (#12386)
Fixes https://github.com/web-platform-tests/wpt/issues/12378, by adding
the right depencies and the right global object depending on context.
--
wpt-commits: d125b8f074d63d145f2b2f52262283add46bbc04
wpt-pr: 12386
Automatic update from web-platform-testsReplace document.origin with self.origin in cookie-helper.sub.js (#12377)
In anticipation of https://github.com/whatwg/dom/issues/410
--
wpt-commits: 0e1ac363581d4bf0851a00a5563619bfef622fe4
wpt-pr: 12377
Automatic update from web-platform-testsHTML: Use /common/blank.html in document open steps tests
--
HTML: More event listener tests for document open steps
--
wpt-commits: 3faeaa9350a80436a52e54708ec5b642c81ea380, dc0ec8ee874c2b2abf5a5e73907ddcdf27575432
wpt-pr: 12122
These methods are only ever used in tests and no longer need to be exposed.
In test_bug445177.xul I tried to preserve more of the test, but everything
after the call to addBroadcastListenerFor is dependent on that.
MozReview-Commit-ID: C4vAxNir4O8
Those tests make sure that an "invalid argument" error is raised
if the body doesn't contain any data.
--HG--
extra : rebase_source : 3446a3e7de70edadf4ac24c1c881633a84f4d352
No need for void* stuff, but I had to keep the semi-manual memory
management to allocate everything inline as we currently do.
Differential Revision: https://phabricator.services.mozilla.com/D3218
Allow i8, u8, i16, u64, i32, and u32 to be implicitly converted into
PrefValue::Int. u64 is not supported because it would overflow,
so this still needs to be handled manually.
geckodriver stores the port number as u8 and this will allow it to
implicitly convert it to PrefValue::Int without using the unsafe
"as i64" coercion.
This moves most of the code to be Rust, except potentially some evaluator
functions, and allows to unblock the use case from any-hover / any-pointer and
remove nsMediaFeatures.
Differential Revision: https://phabricator.services.mozilla.com/D2976
Now that the content is not anonymous we don't need to exclude them explicitly.
This happens because anonymous content inside the shadow tree does report to be
inside the shadow tree, which is true but at the same time slightly footgunny.
In any case the other uses of the use shadow tree stuff are base-uri related,
and changing anon content's base uri in that case sounds like the right thing,
even though anon content shouldn't rely on those anyway.
Differential Revision: https://phabricator.services.mozilla.com/D3409
