Automatic update from web-platform-tests
Update performance.measureMemory to the latest proposal
This changes the result format of the API to the latest version of
the proposal at https://github.com/WICG/performance-measure-memory.
Specifically, per-origin attribution changed to per-frame attribution
with one caveat that cross-origin iframes are considered opaque and
iframes nested in cross-origin iframes do not appear in the result.
The previous version of API:
{
bytes: 70*MB,
breakdown: [
{bytes: 40*MB, globals: 2, type: 'js', origins: ['foo.com']},
{bytes: 30*MB, globals: 1, type: 'js', origins: ['bar.com']}
]
}
The current version of the API:
{
bytes: 70*MB,
breakdown: [
{bytes: 40*MB, type: 'window/js', attribution: ['foo.com']},
{bytes: 30*MB, type: 'window/js', attribution: ['bar.com']}
]
}
Bug: 1049093
Change-Id: I3bbf07ad6e978b9b483561c06cedf6c7a135b7e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087627
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747271}
--
Add two missing long timeouts
--
wpt-commits: d283af7ddbb88540623eb33446868ff9ea6a1df6, 1d9de5dc0876b81e5e188668e6adccde33655969
wpt-pr: 22085
Automatic update from web-platform-tests
[webauthn] WPT - adding port to RP ID should fail
Relying party IDs are defined as "a registrable domain suffix of or
equal to the caller’s origin's effective domain". RP IDs do not include
a port.
This patch changes the host + port subtests to expect a failure instead
of success.
Bug: 875444
Change-Id: I0067ebd883612d534df13a555284fe1cdec7424d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088002
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747289}
--
wpt-commits: 5e8ca5f47a7c8987549f4df92b0baa1c9549048f
wpt-pr: 22092
Remove unused code from automation.py.in, move some android-specific code from
automation.py.in to remoteautomation.py, and eliminate some other easily-replaced
code. In the long term we want to eliminate automation.py.in completely; I may
attempt that once these changes have landed.
Differential Revision: https://phabricator.services.mozilla.com/D66306
--HG--
extra : moz-landing-system : lando
This is a tentative fix, but I think android viewport shenanigans are the only
reason this could be flaky only on Android.
Differential Revision: https://phabricator.services.mozilla.com/D66374
--HG--
extra : moz-landing-system : lando
This patch does the following:
* Moves most logic for initiating about:home / about:newtab into AboutNewTab.jsm
* Makes AboutNewTab the API surface for overriding the default about:newtab URLs.
* Reduces the surface of nsIAboutNewTabService, and makes the properties read-only
* Splits the remaining code in the nsIAboutNewTabService into an implementation for
the parent process, and one for content processes.
This split will hopefully help reduce confusion about which code in
AboutNewTabService is running in which process.
Differential Revision: https://phabricator.services.mozilla.com/D65569
--HG--
rename : browser/components/newtab/test/xpcshell/test_AboutNewTabService.js => browser/components/newtab/test/xpcshell/test_AboutNewTab.js
extra : moz-landing-system : lando
This patch does the following:
* Moves most logic for initiating about:home / about:newtab into AboutNewTab.jsm
* Makes AboutNewTab the API surface for overriding the default about:newtab URLs.
* Reduces the surface of nsIAboutNewTabService, and makes the properties read-only
* Splits the remaining code in the nsIAboutNewTabService into an implementation for
the parent process, and one for content processes.
This split will hopefully help reduce confusion about which code in
AboutNewTabService is running in which process.
Differential Revision: https://phabricator.services.mozilla.com/D65569
--HG--
rename : browser/components/newtab/test/xpcshell/test_AboutNewTabService.js => browser/components/newtab/test/xpcshell/test_AboutNewTab.js
extra : moz-landing-system : lando
BrowserTestUtils.crashFrame now accepts additional `options`, with an argument `crashType` that may
take "CRASH_OOM" or "CRASH_INVALID_POINTER_DEREF"|null to specify the nature of the crash. The names
are taken from CrashTestUtils.jsm but this module cannot be imported as such as it has non-trivial
binary dependencies.
Depends on D54130
Differential Revision: https://phabricator.services.mozilla.com/D54700
--HG--
extra : moz-landing-system : lando
Before Bug 1530908, the build script used `TryToolsMixin.try_message_has_flag`
to dectect a request for artifact builds. Since that is no longer used, we can
remove the dependency.
Differential Revision: https://phabricator.services.mozilla.com/D65842
--HG--
extra : moz-landing-system : lando
The wpt harness spends a lot of time — about 20% of the total runtime
on Linux64 — between tests. The majority of this is shutting down and
restarting the Firefox instance under test. To reduce this
overhead we add the option to preload a Firefox instance which can be
immediately used when a new session is required. This makes the slow
process of creating a profile and starting the browser
asynchronous. Testing shows that this cuts the between-test time to
between a half and a third of the previous value.
The cost of this change is that we are adding background load at the
time tests are running, which could influence the results and add
randomness. However that seems unlikely unless we are right on the
edge of the system performance.
Differential Revision: https://phabricator.services.mozilla.com/D64954
--HG--
extra : moz-landing-system : lando
The taskcluster decision task makes an imperfect decision about when to run test-verify, so
test-verify tasks sometimes find they have no tests to run and bail out early. The existing
bail-out is problematic for ETL ingestion, which expects to see start/finish for each
mozharness step. This patch removes the fatal bail-out (warns instead) allowing all the
mozharness steps to complete; since there's no work to do, steps generally complete quickly.
(I noticed another early return from the same function, for the missing repo/rev case and
updated that as well, for consistency; note that no callers use the function return value.)
Differential Revision: https://phabricator.services.mozilla.com/D66062
--HG--
extra : moz-landing-system : lando
Minor version bumps in preparation for new pypi releases of modules now requiring mozlog 6.0 and/or mozcrash 2.0.
Differential Revision: https://phabricator.services.mozilla.com/D66116
--HG--
extra : moz-landing-system : lando
The wpt harness spends a lot of time — about 20% of the total runtime
on Linux64 — between tests. The majority of this is shutting down and
restarting the Firefox instance under test. To reduce this
overhead we add the option to preload a Firefox instance which can be
immediately used when a new session is required. This makes the slow
process of creating a profile and starting the browser
asynchronous. Testing shows that this cuts the between-test time to
between a half and a third of the previous value.
The cost of this change is that we are adding background load at the
time tests are running, which could influence the results and add
randomness. However that seems unlikely unless we are right on the
edge of the system performance.
Differential Revision: https://phabricator.services.mozilla.com/D64954
--HG--
extra : moz-landing-system : lando
Tons of new passes, some fuzzy bits, and one failure from a test that makes bad
assumptions about themed and unthemed <input type=color> being equally tall.
Differential Revision: https://phabricator.services.mozilla.com/D65724
--HG--
extra : moz-landing-system : lando
This changeset fixes multiple-position-color-stop-radial-2.html which was accidentally passing due to both the test and the reference using invalid syntax.
It also cleans up some other tests that were linking to the wrong spec section.
Differential Revision: https://phabricator.services.mozilla.com/D66038
--HG--
extra : moz-landing-system : lando
Other browsers allow this and the spec doesn't really disallow it, so fix it,
add a test and carry on.
Differential Revision: https://phabricator.services.mozilla.com/D65107
--HG--
extra : moz-landing-system : lando
This patch enables multi-value calls and returns, adding some tests, and
conditionally disabling a couple expect-fail reftests that now pass.
It also changes to make calling multi-result WebAssembly functions from
JavaScript raise a run-time error, and likewise for calling out to
multi-result JS function from wasm. Previously these would abort at
stub generation time.
Differential Revision: https://phabricator.services.mozilla.com/D65502
--HG--
extra : moz-landing-system : lando
This patch removes a `storage.local.clear()` call from raptor-webext for causing a high number of intermittent failures. It also adds a default value for `--host` in the mozharness raptor. Finally, a delayed startup for raptorRunner is added with the hope that this will further decrease intermittents (right now, it might be starting at a very noisy time).
Differential Revision: https://phabricator.services.mozilla.com/D65893
--HG--
extra : moz-landing-system : lando
This removes the obsolete backend. Notes on some of the less obvious changes
made as part of this patch:
- some of the gFoo style getters in Blocklist.jsm were only used by the XML
version of the blocklist; I've removed them and tried to remove spurious
settings of those properties in the remaining tests.
- some utility methods (e.g. distribution information getters) were also only
used for the XML version (for the update URL).
- it's no longer necessary to test switching implementations.
- in browser/base/content/test/plugins/, we ran some tests from two manifests
in order to run them with both blocklist backends. The simplest way of
reducing this back down to one was to remove the remote-settings one. If I'd
been more future-oriented when I created the duplication, perhaps I would
have moved the XML version out into a different manifest instead, but I
didn't, so now it looks like we're removing the modern one, whereas really
we're going to be running the modern one as part of the "normal" tests and
we're no longer running the "old" tests.
- removed all mentions I could see of extensions.blocklist.url which is no
longer used for anything.
- per https://bugzilla.mozilla.org/show_bug.cgi?id=1016555#c23, updated
references for the OneCRL timing and how it relates to blocklist updates.
Differential Revision: https://phabricator.services.mozilla.com/D64933
--HG--
extra : moz-landing-system : lando
This adds an `implementation-status` field to the wpt metadata with 3
possible values; "not-implementing", "backlog" and "implmenting" (the
latter being the same as the default value). It also adds a
`--skip-implementation-status` command line argument to wptrunner that
can be used to skip running tests with the specified implementation
statuses. This is primarilly to allow gecko to avoid running tests (or
run tests less frequently) for things where we don't implement the
spec and don't plan to either ever or in the current roadmap.
Differential Revision: https://phabricator.services.mozilla.com/D65765
--HG--
extra : moz-landing-system : lando
The test is duplicated in two places, so four files to change. The padding in
the non-native theme is just big enough so that the textarea overlaps the float.
In other themes the textarea overflows, but not enough to hit the float.
Differential Revision: https://phabricator.services.mozilla.com/D65663
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add tests for input and change events on checkboxes and radios
This follows @domenic's suggestion in https://github.com/whatwg/html/issues/5291
--
wpt-commits: 78f14c537b62447d64aeb65a30ede77c5d26db41
wpt-pr: 22075
Automatic update from web-platform-tests
Sync on style when creating a pseudo-element animation from script
Sync on style before evaluating a pseudo-element selector other than null.
Remove manual style syncs from pseudo-element animation wpt tests.
Bug: 1057101
Change-Id: I8a1184221f40c7546ac5179615f0d6541e8729e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083715
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747333}
--
wpt-commits: b15e954c41e6d98122ea8e4b4515bb6c6e43cf62
wpt-pr: 22048
Automatic update from web-platform-tests
[Trusted Types] Gate eval on require-tt-for.
Also, tidy up enforcement headers in WPTs, update one.
Bug: 1058437
Change-Id: Ic24b0297af04230562b104fd6664387cba5b169b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089772
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747320}
--
wpt-commits: 261dd95ad3bf4b36b971fe4832dc2f313c491448
wpt-pr: 22102
Automatic update from web-platform-tests
Pointer Event Capture is not lost when using chorded buttons.
Add web test for the bug.
Add check in HandleMouseReleaseEvent to release mouse capture only when all the mouse buttons are released.
Bug: 1053385
Change-Id: Id327f67c915b79673e80b1c97d3e6975a3488d50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2071292
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747291}
--
wpt-commits: 0b243d36ce54f38a58edbea54a51eb0d6940a12a
wpt-pr: 21970
Automatic update from web-platform-tests
Introduce COEP reporting for CORP (3/3)
1: https://crrev.com/c/2074177
2: https://crrev.com/c/2075002
3: [this]
This series of CLs implements https://github.com/mikewest/corpp/pull/9.
We introduce network::mojom::CrossOriginEmbedderPolicyReporter and
its implementation content::CrossOriginEmbedderPolicyReporter, implement
the reporting logic in content::CrossOriginEmbedderPolicyReporter and
the CORP check, and plumb the mojo interface.
This CL creates CrossOriginEmbedderPolicyReport during the frame
navigation and dedicated worker initialization, and give it to the
network service so that (possibly potential) CORP blocks are reported.
Bug: 1052764
Change-Id: Ia39ff8277eb23d96025f5e6fba4e5a4fa6ffde70
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076223
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747176}
--
wpt-commits: 0d183bf3945eda537d23f8d37afbde1dad982544
wpt-pr: 22005
Automatic update from web-platform-tests
Update mozlog from 5.0 to 6.0
--
Update mozcrash from 1.2.0 to 2.0.0
--
jsone bug was fixed upstream
--
wpt-commits: f9d92f30fbfcb0c0d8f38c47bcca86270704528b, bdce0df38105b1a3c4a541223aea72f2ca120203, 8d16f35231fb42cbc68f4cbf1eb90013f777be8c
wpt-pr: 22081
Automatic update from web-platform-tests
Use test() correctly in css-page tests
Update css/css-page/page-rule-declarations-* to use the
test() method properly to test one feature at a time.
--
wpt-commits: 69345f1df225843dcda149d4928ae9e7a74f792f
wpt-pr: 22099
Automatic update from web-platform-tests
[IndexedDB] Fix crash when storing native file system handles using inline keys.
IndexedDB assumes it can non-destructively deserialize a SerializedScriptValue,
however our implementation for deserializing native file system handles actually
modified the SSV in a way that violated that assumption. This fixes this by
cloning the handles in the SSV rather than consuming them.
Bug: 1058419
Change-Id: I11ddfef757849941cc26e920eadb9022f7e138a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088218
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747062}
--
wpt-commits: 51b8e0940e87eda1f843a48d847d653b9a22c8c4
wpt-pr: 22091
Automatic update from web-platform-tests
[webauthn] WPT Fix error for exclude credentials
When an excluded credential is found, the spec says InvalidStateError
should be returned. The test was expecting a NotAllowedError, fix that.
Bug: 875444
Change-Id: I034ea2c270909895f8935a5c5a4d659b6c7327dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088000
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747018}
--
wpt-commits: 1adaa942cb736e31df23b3cca50fd829138b816b
wpt-pr: 22083
Automatic update from web-platform-tests
[web-nfc] Add encoding and lang attributes check (#21874)
* [web-nfc] Add encoding and lang attributes check
--
wpt-commits: 5a3386ed87480e0f23cb501f928e1af8a6f679d3
wpt-pr: 21874
Automatic update from web-platform-tests
[webauthn] WPT - correct unrecognized alg error
When an authenticator does not support a given algorithm, it returns an
error equivalent to "NotSupportedError". Authenticators returning status
not equivalent to "InvalidStateError" remove authenticators from
issuedRequests, which manifests on a timeout ("NotAllowedError").
Correct the createcredential-pubkeycredparams test to reflect this
behaviour.
Bug: 875444
Change-Id: Ia574ca449cf22ddea1b5f434a61704576ca26fa1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088009
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746969}
--
wpt-commits: d487329ed2e95f1dc28151815a27d65bcec5e2d5
wpt-pr: 22088
Automatic update from web-platform-tests
Probably user error, but these weren't showing up in git previ… (#21711)
--
wpt-commits: d9536554b66e3acd13fec3ca1f42931793909cdd
wpt-pr: 21711
Automatic update from web-platform-tests
[webauthn] Clean up CreateCredential WPTs
Remove web platform tests that erroneously expect failures for
converting objects like arrays into dictionaries and other values into
booleans. The webauthn spec does not impose any such restrictions and
the ECMAScript spec precisely specifies how those values are converted.
Bug: 875444
Change-Id: I8c131735808205313314b9043da7e775a51dd9b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2086253
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746888}
--
wpt-commits: 4b661710d457daf4477ba9179f9a281d19fb7367
wpt-pr: 22076
Automatic update from web-platform-tests
[CSP] Factorize SVGElement & MHTMLElement nonce hiding.
According to:
https://github.com/whatwg/html/pull/2373
html and svg Element are hiding their nonce when there are at least one
Content-Security-Policy defined from an HTTP header.
The two implementation:
- HTMLElement::InsertedInto
- SVGElement::InsertedInto
were hidding the nonce slightly differently. To prevent further
divergence, factorize this implementation into Element::HideNonce() and
call it from both places.
Bug: 1053496
Change-Id: I3cbad88f70c61591bef060d4188c82388e6001d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078536
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#746837}
--
wpt-commits: 06705ea82c8a9d1866665c8abd069dd3b0f8c12b
wpt-pr: 22021
Automatic update from web-platform-tests
WPT: Upstream and add some transaction scheduling tests (#22027)
In service of https://github.com/w3c/IndexedDB/issues/253 move some
transaction scheduling tests from Blink to WPT.
This involved converting them from js-test.js to testharness.js, but
the overall logic of each test was retained.
This also adds one new test which verifies the change described
in https://github.com/w3c/IndexedDB/pull/319 - all browsers implicitly
block R-O transactions behind overlapping R/W transactions.
Change-Id: I596aaa75b79bf3bf3e17a2553abb4e11329d59ab
Bug: 921193
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081237
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Auto-Submit: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746553}
Co-authored-by: Joshua Bell <inexorabletash@gmail.com>
--
wpt-commits: 5e1160e543827227c05b10c7660795436a76b307
wpt-pr: 22027
Automatic update from web-platform-tests
[wpt/revlist] Add a flag to turn on debug logging (#22040)
./wpt revlist --verbose
--
wpt-commits: f72ec09c929aa0c9de70642a48c7945a9faa7018
wpt-pr: 22040
Automatic update from web-platform-tests
cc Add tests for autocomplete attribute
--
wpt-commits: 34f3acabcceff6504c38bd826aca9c0728f26234
wpt-pr: 22056
Automatic update from web-platform-tests
Revert "Fix outline when linebox has non-zero inline offset"
This reverts commit fbbcb3271fa5971163b5784b2fcfd10b2e06938a.
Reason for revert: Regressed crbug.com/1057576
Original change's description:
> Fix outline when linebox has non-zero inline offset
>
> When computing outline rects in an inline formatting context,
> the coordinate system needs to be relative to the root of the
> inline formatting context, because the algorithm needs to
> call |LayoutObject| functions, which uses the coordinate
> system for inline |LayoutObject|s.
>
> This patch fixes not to accumulate line box offset. For the
> inline direction, this is usually zero and is not visible,
> but non-zero `padding-left` can expose this difference.
>
> Bug: 1048070
> Change-Id: I30dfabcca621136b6d78892a1856c1336c7438eb
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038296
> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
> Reviewed-by: Aleks Totic <atotic@chromium.org>
> Commit-Queue: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#738646}
TBR=wangxianzhu@chromium.org,cbiesinger@chromium.org,kojii@chromium.org,atotic@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 1048070, 1057576
Change-Id: I183b2c0e5ba65e8dd97418e222331ec566d2adbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2084775
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746563}
--
wpt-commits: 1cb304fbdb620f02f8ec49b38195936dd9069c91
wpt-pr: 22073
moz-wptsync-bot
Ulan Degenbaev
Nina Satragno
Geoff Brown
shindli
Chris Fronk
Emilio Cobos Álvarez
Jan-Erik Rediger
Ryan Hunt
Mike Conley
Dorel Luca
Nicholas Nethercote
Tom Schuster
Mike Shal
Ben Hearsum
Daniel Varga
David Teller
Tom Prince
James Graham
Paul Adenot
Kershaw Chang
Bogdan Tara
Florin Strugariu
Narcis Beleuzu
Andrew Osmond
Brindusan Cristian
Tim Nguyen
Noemi Erli
John Dai
Andy Wingo
Gregory Mierzwinski
Gijs Kruitbosch
Julian Descottes
Mark Banner
Jan-Ivar Bruaroey
Joey Arhar
George Steel
Stefano Sanfilippo
Liviu Tinta
Krzysztof Kotowicz
Yutaka Hirano
pyup-bot
Philip Jägenstedt
Felipe Erias
Marijn Kruisselbrink
Wanming Lin
Tab Atkins Jr
arthursonzogni
Blink WPT Bot
autofoolip
Robert Ma
Mark Rogers
Koji Ishii