Automatic update from web-platform-tests
Add some tests for Symbol properties on Storage objects.
--
wpt-commits: 4582ca92624594ad7e5d2c1137823c1c1e93d2e3
wpt-pr: 15131
Automatic update from web-platform-tests
Use promise_rejects in portals-activate-no-browsing-context.html.
Change-Id: Iccdbbe823d3d4ed2554c2527d90da8b7692a2e4e
Reviewed-on: https://chromium-review.googlesource.com/c/1450282
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Auto-Submit: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628489}
--
wpt-commits: cee3936fb6efe737b8fd9c26e1f4f3fa8d878fda
wpt-pr: 15213
Automatic update from web-platform-tests
Urange Parsing
Fairly exhaustively test <urange> parsing, and make sure UAs aren't cheating with specialized tokens.
--
Stabilize the starting value on "valid" tests
Make sure that tests for should-be-valid syntax start from a stable value as well, so they don't depend on test ordering so much.
--
meta => link
--
Fix selector serialization
Was pretty sure selectors serialized with spaces around the combinator, but wasn't sure, and Chrome failed the test anyway. Firefox passes but with spaces, so make sure I match that.
--
Force uppercase of the urange
Urange serialization isn't specified, so I shouldn't rely on the casing in this test, at least. Instead, just uppercase things, since casing doesn't matter.
--
fix accidental collision
--
Merge pull request #15195 from web-platform-tests/tabatkins-patch-1
Urange Parsing
--
wpt-commits: be6aae49e28d40a3e32d49205ceea50ad98070f9, 794729af2f994e4912d15d27527be1c847a027e9, c62259ab5c622bab80af2e9489dea2a9cf8f2594, 23a94e6348cccd97251024147ddf0b855b31ba55, d9769535a761f5ae3969463108239d2ba2563ff7, bdf1782f0a7df711aa700c67ceddfdbeb5a3f1b3, 62bfaebd63ab3f077fbb439d9d9a65acc97c5b7c
wpt-pr: 15195
Automatic update from web-platform-tests
Portals: Hide portal host before dispatching activate event
window.portalHost returns null in the portal browsing context after it
has been activated.
Bug: 914117
Change-Id: I2758d2bb29ad0381cff51f0c312fa88c3bacaed4
Reviewed-on: https://chromium-review.googlesource.com/c/1412792
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628378}
--
wpt-commits: 4ad2eef86295a88acad1c373fb9fde9ca471a630
wpt-pr: 15203
Automatic update from web-platform-tests
Allow audio requests in getDisplayMedia() calls from blink
This CL adds cases to allow for getDisplayMedia({video:true, audio:true}) calls.
- Remove the earlier checks in blink that adds exceptions for audio requests.
- Reject audio-only requests.
- Set up UserMediaRequest appropriately and allow for settings in
MediaStreamManager.
- Add a FakeUI case to create a dummy AudioDevice.
- Add unit tests and layout tests.
Bug: 896333
Change-Id: I627c8ce84d752528430c4d46c0c5f472b39706d1
Reviewed-on: https://chromium-review.googlesource.com/c/1444353
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628366}
--
wpt-commits: 959f47bd77009e5e4c1b7a62db5b1a893b41efd9
wpt-pr: 15146
Automatic update from web-platform-tests
Reland "Portals: Expose portalHost to portal's browsing context"
This is a reland of 9d4738420905a6b28407a8282512d8307d413780
Original change's description:
> Portals: Expose portalHost to portal's browsing context
>
> window.portalHost returns a PortalHost to script running inside the main
> frame within a portal.
>
> Bug: 914117
> Change-Id: I26fb4ae9676261bee4446bfbc6ee34b28dc618b1
> Reviewed-on: https://chromium-review.googlesource.com/c/1399569
> Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Charlie Reis <creis@chromium.org>
> Reviewed-by: Lucas Gadani <lfg@chromium.org>
> Reviewed-by: Jeremy Roman <jbroman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#624316}
Bug: 914117
Change-Id: I2830cafac26928229d474fd91921fbf2f9a47952
Reviewed-on: https://chromium-review.googlesource.com/c/1425041
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628329}
--
wpt-commits: b0020d5df18998609b38786878f7a0b92cc680aa
wpt-pr: 14974
Automatic update from web-platform-tests
Add support for all RTCIceCandidate fields.
Intent to implement and ship thread:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/T6zlVFZhRVY
Drive-by: Fix a few minor lint issues.
Bug: 683094
Change-Id: I1c8cb27e8583f200d6e4d9fe6f2d1b633e8dab66
Reviewed-on: https://chromium-review.googlesource.com/c/1429969
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628324}
--
wpt-commits: 932df409e4c23f7cba3fe2e634426b4429694df0
wpt-pr: 15132
Automatic update from web-platform-tests
[Azure Pipelines] Add required variables for manually triggering jobs (#15201)
This is enable adding more manual jobs without triggering all of them.
--
wpt-commits: e1d9e660a5b1eb9ee26193f2c71d26673f764e19
wpt-pr: 15201
Automatic update from web-platform-tests
[Azure Pipelines] Run all tests on Edge on Windows 10 (#15196)
This job is only triggered manually until it has been shown to be robust.
--
wpt-commits: 8e6c6429b335f439ed332bc79214730225a1405d
wpt-pr: 15196
Automatic update from web-platform-tests
cache storage: Introduce MultiCacheQueryOptions as per spec
MultiCacheQueryOptions inherits CacheQueryOptions and contains cacheName[1].
MultiCacheQueryOptions in match of CacheStorage replaces CacheQueryOptions.
On the other hand, match in Cache takes CacheQueryOptions without cacheName.
[1]: https://w3c.github.io/ServiceWorker/#cachestorage
It was added in https://github.com/w3c/ServiceWorker/pull/1341
Bug: 919077
Change-Id: I86b68fe9197dacb431f989fa3958daebe0fd1dba
Reviewed-on: https://chromium-review.googlesource.com/c/1395998
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Commit-Queue: Amos Lim <eui-sang.lim@samsung.com>
Cr-Commit-Position: refs/heads/master@{#628245}
--
wpt-commits: 8641724d2bbd1c6a2aff47286bacbb26123a5b9c
wpt-pr: 15112
Automatic update from web-platform-tests
Portals: Send detach message to browser process for portals
We don't currently send a message because the RenderFrameProxy created
has no parent (so it looks like a main frame). This ensures that
same-origin frames within the portal are also detached.
The test added would fail with --enable-leak-detection without this
change (the iframe inside the portal would leak).
Bug: 923898
Change-Id: I2b56b8e303b40d275976da5ed8a0fdde7726b51c
Reviewed-on: https://chromium-review.googlesource.com/c/1430586
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628179}
--
wpt-commits: bf09c7c954ec1bf3860448d9db98d040c5ad5354
wpt-pr: 15026
Automatic update from web-platform-tests
Fix edge cases for interpolation of rotation transforms.
* Allow blending of rotations around different axis.
* Handles interpolation of rotation transforms with misaligned axes, but where one of the rotation angles is zero. By spec, this should used the axis associated with the non-zero axis.
* Cleanup handling of rotation around a common axis.
See https://drafts.csswg.org/css-transforms-2/#interpolation-of-transform-functions.
Bug: 897358
Change-Id: Ifc01754927c254300670df5016bce929df8314d6
Reviewed-on: https://chromium-review.googlesource.com/c/1435711
Reviewed-by: Ian Vollick <vollick@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628047}
--
wpt-commits: ec0c466f7149fc0d65cacc4dc78755710310930d
wpt-pr: 15136
Automatic update from web-platform-tests
WritableStream: fix two small coverage gaps
Verify that stream.abort() fails if the stream is locked.
Verify that the .locked getter becomes true when a writer is acquired.
--
wpt-commits: 54f4e2a7268165a06a292bb5d31c2cab1a2e59c8
wpt-pr: 15186
Automatic update from web-platform-tests
Don't skip invalid functions when looking for var references.
This matches the spec, WebKit and Firefox.
From https://drafts.csswg.org/css-variables/#using-variables:
> If a property contains one or more var() functions, and those functions are
> syntactically valid, the entire property’s grammar must be assumed to be
> valid at parse time. It is only syntax-checked at computed-value time, after
> var() functions have been substituted.
Bug: 921152
Change-Id: Ie46268ffae4e01f457f379c674e0cf1a7ccea354
Reviewed-on: https://chromium-review.googlesource.com/c/1446653
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#628023}
--
wpt-commits: 53de730057f1abca14d8bf9f25077148cd3163c3
wpt-pr: 15162
Automatic update from web-platform-tests
Link element events should be able to fire more than once
As per spec https://html.spec.whatwg.org/multipage/links.html#link-type-stylesheet,
the <link> element can have its load and error events fire multiple times,
per resource it loads.
Bug: 922618
Change-Id: Ifc9ade076e119d5cf9f4eaf656c6ea7c1deb0ba9
Reviewed-on: https://chromium-review.googlesource.com/c/1423601
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
Cr-Commit-Position: refs/heads/master@{#628010}
--
wpt-commits: 8c2f92077bd45be902b98018e62676f041a6a816
wpt-pr: 14958
Automatic update from web-platform-tests
Make Japanese linebreaking tests more robust against rounding
These tests were comparing offsetLeft, but there were pixel differences
which made some of the tests fails. Using a less than 1
getClientBoundingRect().left difference instead, cleaning up the code
and removing expectations file due to these robustly passing now. The
pixel differences are not relevant to the intention of the test.
Bug: 927287
Change-Id: I5235489457183aa7a3ea25b40ccfa96dfef3f980
Reviewed-on: https://chromium-review.googlesource.com/c/1448451
Auto-Submit: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627998}
--
wpt-commits: 74449e61abd3b495373253f83dd0d5638668e79d
wpt-pr: 15187
Automatic update from web-platform-tests
[PE] Update background obscuration and check for change during PrePaint
Background obscuration status is affected by many factors. Previously
we cached the status, but invalidation of the cache was not complete,
and it was difficult to keep it complete.
Now we update background obscuration status during PrePaint, whenever
the object is marked for any reason for PrePaintTreeWalk, which should
cover all conditions that cause background obscuration change.
Bug: 916050
Change-Id: Id044c9e724940f7a83c8dfc1aca8f3dde3526e96
Reviewed-on: https://chromium-review.googlesource.com/c/1444300
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627993}
--
wpt-commits: 7bd9a7a85093706f52ffa9c13af7c34304cb488b
wpt-pr: 15168
Automatic update from web-platform-tests
Make Chinese linebreaking tests more robust against rounding
These tests were comparing offsetLeft, but there were pixel differences
which made some of the tests fails. Using a less than 1
getClientBoundingRect().left difference instead, cleaning up the code
and removing expectations file due to these robustly passing now. The
pixel differences are not relevant to the intention of the test.
Bug: 927287
Change-Id: I74fe8d64edb1a52de4fd0dbb3143843b305f8156
Reviewed-on: https://chromium-review.googlesource.com/c/1448215
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Auto-Submit: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627968}
--
wpt-commits: 7a7d3b23c4fdec31f85ca1083c91dffe6ecf67c7
wpt-pr: 15184
Automatic update from web-platform-tests
Get Edge version using PowerShell command (#15172)
Adapted from https://stackoverflow.com/a/52056711/191722.
With the Windows 10 VMs currently in the self-hosted agent pool for
Azure Pipelines, it returns "44.17763.1.0".
--
wpt-commits: 049e43f29e4f19ec6600a7009a20271bce5e91cc
wpt-pr: 15172
Automatic update from web-platform-tests
Improve the test names of tests for toJSON behavior. (#14866)
In particular, this avoids duplicate test names when testing with multiple objects (ref #14645).
--
wpt-commits: 7fb15bfac1e7380aa74176886120edab9afb5d02
wpt-pr: 14866
Automatic update from web-platform-tests
[Azure Pipelines] Run infrastructure/ tests on Windows 10 (#14300)
This job is only triggered manually until it has been shown to be robust.
--
wpt-commits: b5e00132e6843e622cdb952766eb99118b62fddf
wpt-pr: 14300
Automatic update from web-platform-tests
[LayoutNG] Provide both inline resolution sizes to legacy.
When entering legacy layout from NG, we need to provide both percentage
resolution inline size and available inline size.
Available size is used when using the fill-available measure, i.e. what
typically takes place when inline-size is auto. Percentage resolution
size is used otherwise (to resolve percentages). We used to provide
percentage size if inline-size was percentage based, and available size
otherwise. But there are cases where we need both. Any of inline-size,
inline-min-size and inline-max-size may or may not be percentage based,
and letting the unit type of inline-size decide therefore won't do.
Change-Id: I225372584a88471dad35deddbc2d3a7de732583a
Reviewed-on: https://chromium-review.googlesource.com/c/1443992
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627885}
--
wpt-commits: 6b32df28ee471247e7d6e5e1764f1c47ea762f5d
wpt-pr: 15160
Automatic update from web-platform-tests
HTML: window.open() can set opener of a nested browsing context
Needed for https://github.com/whatwg/html/pull/4284.
--
wpt-commits: 5cf7f41336801449ce7499a5f41ccf6848650e9c
wpt-pr: 15078
Automatic update from web-platform-tests
innerHTML serialization should not have a special handling for javascript: URLs.
The HTML specification [1] doesn't have such special handling, and
Firefox conforms to the specification.
Remove fast/innerHTML/javascript-url.html because javascript: URLs are
not special any longer.
[1] https://html.spec.whatwg.org/multipage/parsing.html#serialising-html-fragments:attribute's-serialised-name
Bug: crbug.com/927164
Change-Id: I63317517dc1549190e66f5fdfa44f6bb38545394
Reviewed-on: https://chromium-review.googlesource.com/c/1447164
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627794}
--
wpt-commits: ec735e1c986519995190a1a1089034cb29879914
wpt-pr: 15177
Automatic update from web-platform-tests
Fixing test to use wpt server features.
Change-Id: I6c40eacb5635461375543d857b37bb2bd36a2805
Reviewed-on: https://chromium-review.googlesource.com/c/1446773
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627717}
--
wpt-commits: c0d2352f34b33d8cd346b38db301cfa2c5be92f2
wpt-pr: 15164
Automatic update from web-platform-tests
[LayoutNG] Fixed elements inside split inlines triggered DCHECK
The bug was that position:fixed elements were not getting laid out.
It was caused by split inlines containing block fix.
I've modified an existing testcase that we used to test split
inlines to also test fixed.
Bug: 923268
Change-Id: Ic1fe1bbdf1ffc2dfe80e4dbe5c03065be05c082c
Reviewed-on: https://chromium-review.googlesource.com/c/1445393
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627663}
--
wpt-commits: ac12b3e9488edb436f063b11213e954ae62d5a5e
wpt-pr: 15151
moz-wptsync-bot
Ms2ger
Jeremy Roman
Tab Atkins Jr
Yi Gu
Kevin Ellis
Adithya Srinivasan
Emircan Uysaler
Guido Urdaneta
Philip Jägenstedt
autofoolip
Amos Lim
Gérard Talbot
Nicolas Pena
Adam Rice
Emilio Cobos Álvarez
Dominic Farolino
Ben Smith
Dominik Röttsches
Xianzhu Wang
Florent Castelli
Morten Stenshorne
Anne van Kesteren
Kent Tamura
kdillon
Aleks Totic