Automatic update from web-platform-testsAdd tests for no active script in import() (#14157)
Follows https://github.com/whatwg/html/pull/4181.
--
wpt-commits: 5241a3fe2c638f9fadcc040f39f3e6a71a2be2e1
wpt-pr: 14157
Automatic update from web-platform-testsFind manifest for download by tags instead of commits
This makes it possible to use `./wpt manifest` on a checkout that is
more than 50 commits behind master. The downside is that it will require
more network requests if the most recent tag/tags don't have releases
uploaded.
Add more warnings to make it clearer why it goes wrong when it does.
--
wpt-commits: 3657828ff4243fcc2f3b3fa4e7bed34d646ad565
wpt-pr: 14025
Automatic update from web-platform-testsAutomate one fullscreen test using `test_driver.bless` (#14072)
Part of https://github.com/web-platform-tests/wpt/issues/7281.
--
wpt-commits: 39e6009b920f632e6c2fee6cd3d96418d677d04f
wpt-pr: 14072
Automatic update from web-platform-testsFix Feature Policy report output
This brings the feature policy report format in line with the spec,
and fixes the tests which were broken by WPT import.
Bug: 907232
Change-Id: If9d9469956221c18a1aa72ee39debb1340efc01f
Reviewed-on: https://chromium-review.googlesource.com/c/1338167
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610427}
--
wpt-commits: 1832abd9419a532881abe413ef20e717ee8d2a3e
wpt-pr: 14154
Automatic update from web-platform-tests[streams] Refactor to multi-global test format (#14172)
* Rename streams tests to .any.js
* Use metadata to import resources in streams tests
* Run streams tests in all scopes
* Delete old test wrappers
* Delete old test wrapper generator
* Replace setTimeout with step_timeout
* Use t.step_timeout in tests
* Remove obsolete done calls
--
wpt-commits: a89730a0f3638d709ccc42064c8f8eb8935b04f7
wpt-pr: 14172
Automatic update from web-platform-testsAdd a list of BackgroundFetchRecord objects to BackgroundFetchRegistration.
When we allow access to active background fetches, BackgroundFetchRecords for
the fetch can be accessed from multiple places. It simplifies matters if
we return the same record for a request whenever it's accessed.
This CL adds a (private) list of BackgroundFetchRecords to the
BackgroundFetchRegistration object, and updates it every time match and
matchAll() are called.
The second change introduced here is to not immediately resolve
responseReady() if the fetch is active and a response for the request
isn't yet available. Once the fetch has completed, or there's a response
available for the request, we resolve pending promises. We also make sure to
return the same promise (resolved or unresolved) for a given record,
every time responseReady is called.
For a more detailed discussion, see the following doc:
https://docs.google.com/document/d/1CrbWrnnshhyp_SfiAeuODpnQX36GK3Bsi19rXQGez6Q/edit?usp=sharing
Bug: 875201
Change-Id: I8cb386efd19086c0993ad2be2fb2691ad90597ec
Reviewed-on: https://chromium-review.googlesource.com/c/1336151
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610410}
--
wpt-commits: 12720fdc8914deec3e7cc627036a26217cc1e908
wpt-pr: 14060
Automatic update from web-platform-testsMake ReadableStream extendable
IDL defined ReadableStream was not extendable because it didn't use
provided |info.Holder()| as its wrapper. Instead, it creates a new
wrapper in Create functions.
This CL solves the issue by making the constructor "custom". The custom
constructor creates a blink::ReadableStream first, then associates it
to the wrapper, and then calls the appropriate Init function.
Bug: 906476
Change-Id: I91a7fec1cf4ee5e08704a944b0af852584d1679e
Reviewed-on: https://chromium-review.googlesource.com/c/1347643
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610391}
--
wpt-commits: a51c2df43ad4491d9a778f0f93e83b596fe47c2b
wpt-pr: 14185
Automatic update from web-platform-testsExpose all constants on SVGFEBlendElement
Per:
https://drafts.fxtf.org/filter-effects/#InterfaceSVGFEBlendElement
All other browsers expose these already.
Bug: 906612
Change-Id: I4be6185d4832d980a5d7c6518dcb0b2ccca2ce82
Reviewed-on: https://chromium-review.googlesource.com/c/1341846
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610379}
--
wpt-commits: 21705cd7f9e2319c8e0bdb7f315f4217707fbe76
wpt-pr: 14148
Automatic update from web-platform-testsWPT: service worker: canvas tainting with two images from the same URL
This adds a test that does the following:
- Writes to a canvas with a cors same-origin image
- Writes to a canvas with a cors cross-origin image from the same URL
- Tests that the canvas is tainted after the second step.
Bug: 907047
Change-Id: Ie231b442eb9b55c642b3957c065555e6f4997a83
Reviewed-on: https://chromium-review.googlesource.com/c/1347952
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#610356}
--
wpt-commits: d65f24c346dff3b5dce2983b413805b97c223417
wpt-pr: 14183
Automatic update from web-platform-testsAdd scroll-animations reviewers
Antoine and Stephen have recently been added as editors of the spec
--
wpt-commits: c34207cd731d8aebfb6a8b7eb706259149b6240b
wpt-pr: 14189
Automatic update from web-platform-tests[cookies] Add test for default path calculation (#14182)
* [cookies] Add test for default path calculation
* fixup! [cookies] Add test for default path calculation
--
wpt-commits: ad1f7dc356c8f61a5f822def378ebde50c610420
wpt-pr: 14182
Automatic update from web-platform-testsCreate EventTiming folder (#14176)
In particular, the META file includes the explainer in place of the spec (no spec yet).
--
wpt-commits: 579140910974daa5394f741197b0b68179882490
wpt-pr: 14176
At this point, we've freshly allocated data for the generated JSON.
There's no need to copy it into a separate nsCString; we can simply
adopt the generated JSON into the nsCString, saving a copy.
Moves bspatch.h and bspatch.cpp into new folder
Adds LICENSE, moz.yaml, and moz.build for bspatch
Alters bsdiff and updater build files to account for the new location of bspatch
Renames toolkit/mozapps/update/common/errors.h to toolkit/mozapps/update/common/updatererrors.h for
breaking windows builds. It collided with MSVCRT's exported errors.h after being added to the export list for
the 'updatercommon' library
Differential Revision: https://phabricator.services.mozilla.com/D13735
--HG--
rename : toolkit/mozapps/update/common/errors.h => toolkit/mozapps/update/common/updatererrors.h
rename : toolkit/mozapps/update/updater/bspatch.cpp => toolkit/mozapps/update/updater/bspatch/bspatch.cpp
rename : toolkit/mozapps/update/updater/bspatch.h => toolkit/mozapps/update/updater/bspatch/bspatch.h
extra : moz-landing-system : lando
When wpt is used by developers they often want to reload a test that's
running to allow iterative development (or running under devtools,
etc.). The recent switch to target marionette commands at the test
window rather than the opener window broke this as waiting is
implemented as an async script that never returns (i.e. a promise that
never resolves) and when this is in the test window navigating that
window causes the script to return.
A simple, but not particuarly elegant, solution here is to simply
rerun the script in the new window.
Differential Revision: https://phabricator.services.mozilla.com/D14087
--HG--
extra : moz-landing-system : lando
In Bug 919979 we added 100 bytes to the size returned by CalcBufferSize
to work around an error with the calculated buffer size with small
resolutions. I verified that this extra buffer is no longer required with
a modified mochitest. Given the age of the bug this was working around,
I don't think a permanent test is required to prevent regressions from
upstream.
Differential Revision: https://phabricator.services.mozilla.com/D14076
--HG--
extra : moz-landing-system : lando
- Unified openContainerNodeInTabs and openURINodesInTabs in PlacesUIUtils into openMultipleLinksInTabs
- Users are now warned when the amount of links to be opened is equal to or exceeds browser.tabs.maxOpenBeforeWarn
Differential Revision: https://phabricator.services.mozilla.com/D12983
--HG--
extra : moz-landing-system : lando
Whilst we do set the Keep-Alive HTTP header to request the HTTPD to
use a persistent connection, we throw away the httplib.HTTPConnection
object after each request. This will causes the HTTPD to serve us
a persistent connection, only to throw it away after the first request.
When the connection timeout is reached, httplib closes the connection
for us. Unfortunately httplib does not reconnect for the next
request, so we need to manually check if the underlying socket
connection to the server is alive.
We check whether the connection has dropped or if it has unread,
buffered data using select() as a poller. We could use poll() here
on available systems, which might give a theoretical performance
improvement since it gives O(number of file descriptors), but since
we only deal with one connection select() will probably be good enough.
Differential Revision: https://phabricator.services.mozilla.com/D13845
--HG--
extra : moz-landing-system : lando
Domenic Denicola
Philip Jägenstedt
moz-wptsync-bot
Ian Clelland
Jan-Ivar Bruaroey
Mattias Buelens
Mugdha Lakhani
Yutaka Hirano
Hiroki Nakagawa
Fredrik Söderquist
Matt Falkenhagen
kaixinjxq
Brian Birtles
autofoolip
jugglinmike
npm1
Brindusan Cristian
Nathan Froyd
Geoff Brown
Boris Zbarsky
June Wilde
Dave Townsend
James Graham
Dan Minor
Jason Orendorff
Matt Woodrow
Sebastian Hengst
Yura Zenevich
Emilio Cobos Álvarez
Toby Ward
Florens Verschelde
Cosmin Sabou
Andreas Tolfsen