Automatic update from web-platform-tests
Add some tests for named properties on Storage.
--
fixup! Add some tests for named properties on Storage.
--
Add some tests for named properties on Storage. (#15014)
--
wpt-commits: 07cf5c1e4289b504c72b86cbe487d35fa5d2395c, 66e29f00f5ac4b42175342c15927b9efaf4dc19f, 70cc8f087f69a681dfe58aa75dbdab466419b3dd
wpt-pr: 15014
Automatic update from web-platform-tests
@charset isn't a valid rule and should be dropped
--
Spaces, not tabs :(
--
Merge pull request #15058 from web-platform-tests/tabatkins-patch-2
@charset isn't a valid rule and should be dropped
--
wpt-commits: 77561fc06acd05384ce8c70479d8bcb10325b81b, b483a4f829a044371555c5a7b90e57c53a66a804, 388ba3a049a3473b1945b9f8f81e9d6e342a249e
wpt-pr: 15058
Automatic update from web-platform-tests
Make webrtc-stats idlharness.js test depend on webrtc (#14983)
Required for https://github.com/web-platform-tests/wpt/pull/14960.
--
wpt-commits: 40b0c100e15c98a91bf8804b31e0f41e8bdbaab6
wpt-pr: 14983
Automatic update from web-platform-tests
Updating WebDriver new window command tests to switch window (#15043)
As originally implemented, the tests set the `handle` property of
the session instead of the `window_handle` property. So they don't
switch to the new window context before checking the
url, opener, and name. This commit fixes it.
--
wpt-commits: 363fd4ea3dd3f3ee5fde4f56bf26a3ad690b3b78
wpt-pr: 15043
Automatic update from web-platform-tests
Use fluxbox as window manager for xvfb in CI (#14981)
--
wpt-commits: 8b4c3d8215517554199d7f35f686be12e69473d5
wpt-pr: 14981
Automatic update from web-platform-tests
[IndexedDB]: Explicit commit error timing handling.
When a transaction is explicitly committed, there may yet be unhandled
errors that the browser has sent but the renderer has not yet seen. This
can cause strange behaviour (see the Github discussion link below). This
patch keeps track of the 'handled errors' in the renderer and the 'sent
errors' in the backend. The 'handled errors' number is sent when the
transaction is explicitly committed, and the browser can compare this
with the 'sent errors'. If they don't match, the transaction is aborted
GitHub Discussion: https://github.com/w3c/IndexedDB/pull/242
Bug: 911877
Change-Id: I7ea7b9e20c70528de3f363e961f87a3d8f5798d3
Reviewed-on: https://chromium-review.googlesource.com/c/1378806
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Andreas Butler <andreasbutler@google.com>
Cr-Commit-Position: refs/heads/master@{#625780}
--
wpt-commits: b0fbbb9ff451b18bf8a69fd54027bf59d21c2667
wpt-pr: 14761
Automatic update from web-platform-tests
[animation-worklet] Basic pause implementation
Pausing worklet animation now holds the time. This works as expected for
main thread animations. Implementing this for composited worklet
animations will be done in a follow up patch.
Major changes:
- Add and expose pause() method pausing the animation.
- Introduce hold_time that is used when animation is paused.
- Rework how current time is computed, it is now closer to
regular animations i.e., we either compute it based on
"start time and timeline.currentTime" or use "hold time".
- Instead of setting start time we now set the current time
which then works backward to compute either the start time
or the hold time based on the animation state.
- When transitioning animation play state, we now always set
the current time. Previously this was adhoc and inconsistent.
- Introduce has_started_ to differentiate when playing an
animation for the first time vs playing it from pause.
TEST:
* wpt/animation-worklet/worklet-animation-pause.https.html: js test for basic current time calculations
* wpt/animation-worklet/worklet-animation-pause-immediately.https.html: reftest for basic pause
* wpt/animation-worklet/worklet-animation-pause-result.https.html: reftest for pause/resume.
* WorkletAnimationTest.PausePlay: unit test for basic state transition and time calc
Bug: 821910
Change-Id: Ie4b00129398159b3b5b83212bb63c43f2ce8bf4e
Reviewed-on: https://chromium-review.googlesource.com/c/1383298
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625711}
--
wpt-commits: 309c4624b9172bd1a7852ae8438932543b04f4bd
wpt-pr: 14932
Automatic update from web-platform-tests
Reland [css-text] New value 'break-spaces' for the white-space property
This is a reland of a07642661ef7ff08c156e90394504a3a40afc9ea
The build failure that caused the revert has been fixed in
https://crrev.com/c/1430010TBR=kojii@chromium.org
Original change's description:
> [css-text] New value 'break-spaces' for the white-space property
>
> Finally the CSS WG decided [1] to move back the 'break-spaces' value to
> the 'white-space' property. This makes the parsing logic easier than
> the previous approach of using the 'overflow-wrap' property.
>
> This new value prevents the white-space sequence to collapse and gives
> breaking opportunities after every preserved white-space.
>
> https://drafts.csswg.org/css-text-3/#valdef-white-space-break-spaces
>
> Additionally, unlike 'pre-wrap', non-collapsible spaces or tabs at the
> end of a line cannot be hung or visually collapsed, since we want them
> to be preserved and broken.
>
> [1] https://github.com/w3c/csswg-drafts/pull/2841
>
> Bug: 767634
> Change-Id: I55e888d4472de11c64c4b14e2710c6e3d1832e67
> Reviewed-on: https://chromium-review.googlesource.com/c/1136543
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
> Cr-Commit-Position: refs/heads/master@{#623324}
Bug: 767634
Change-Id: I987214a1b1275bfcc34cb2cadb2089344c4a7da4
Reviewed-on: https://chromium-review.googlesource.com/c/1415254
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#625718}
--
wpt-commits: 2e3722e50cb8fd2e3c70629c2ca2607e79c6d5e2
wpt-pr: 15042
Automatic update from web-platform-tests
Implementing support for 'Cross-Origin-Resource-Policy' response header.
See also
https://fetch.spec.whatwg.org/#cross-origin-resource-policy-header
Bug: 853723
Change-Id: I1bafc0c75c84dc0fff36fcf92fab34ea4206d689
Reviewed-on: https://chromium-review.googlesource.com/c/1416813
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625676}
--
wpt-commits: 52a9ba72bea13a28d2dbd7f9b4235f542a32ecd6
wpt-pr: 15007
Automatic update from web-platform-tests
Feature Policy JS API Update: Add document.featurePolicy.features
This adds a method to return the names of all policy-controlled
features supported by the browser. Because this list is determined by
the set of features implemented by Chrome, rather than conformance to
any particular spec, the tests are in /webexposed/ rather than WPT.
(Existing IDL tests in WPT cover the existence of the new method and
the data types that it returns, without depending on the exact values
returned.)
Bug: 917070
Change-Id: I35ccbdce794e236500d15afe5419057a8f162ae7
Reviewed-on: https://chromium-review.googlesource.com/c/1387151
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625667}
--
wpt-commits: f4c41eec30303b282c8107f35c788ffd125dd567
wpt-pr: 14827
Automatic update from web-platform-tests
Add a test for ServiceWorker and AppCache interaction with claim()
Bug: 917284
Change-Id: I953dfecdf1ae825343ae659d496d089ce356e662
Reviewed-on: https://chromium-review.googlesource.com/c/1388129
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#619022}
--
wpt-commits: 95d10c70fd3ebebcb74f0ca2fe90bb3b495afe26
wpt-pr: 14638
Automatic update from web-platform-tests
Change the condition for running all tests for branch to reason (#15041)
This is slightly cleaner in that the branch name is only used in one
place (the scheduled trigger) but more importantly makes it possible
to debug this by scheduling jobs for other branches at any time.
--
wpt-commits: 29d7d9439f528ed669e50dbb28c3c197d40e71a3
wpt-pr: 15041
Automatic update from web-platform-tests
Update pyflakes from 2.0.0 to 2.1.0
--
Fix comparison with int to use == rather than relying on interning
--
wpt-commits: bae08c312f922ab1517ef2e5a14588eadc8d02c0, 2603f1314ebda48d20e2645d34ae8dda413e3484
wpt-pr: 15031
Automatic update from web-platform-tests
Invoke the staging.wpt.fyi Azure hook at the end of daily run (#15037)
This needs to be changed to use wpt.fyi when verified.
Towards https://github.com/web-platform-tests/wpt/issues/14836.
--
wpt-commits: 95edbe97fbad8eb2b77d901da5c4479a53182e65
wpt-pr: 15037
Automatic update from web-platform-tests
[eme] Check if HDCP policy is supported (#14384)
In [1] there is a proposal to add the ability to know before fetching content
if HDCP (and what version) can be enforced. This adds a test to check if it
is supported.
[1] https://github.com/WICG/hdcp-detection/blob/master/explainer.md
--
wpt-commits: 2cc428dbf25bc3004bd057d6d3b42a1417fc4cc0
wpt-pr: 14384
Automatic update from web-platform-tests
[eme] Check if encryption scheme is supported (#14383)
In [1] there is a proposal to add the ability for querying the encryption
schemes supported by the CDM to MediaKeySystemConfiguration. Adding a test
to check this.
[1] https://github.com/WICG/encrypted-media-encryption-scheme/blob/master/explainer.md
--
wpt-commits: 01e59d35144b76c85c48a6f2b742aee230194f79
wpt-pr: 14383
Automatic update from web-platform-tests
[CSS] Make ::part work with other pseudo elements.
Now selection, first-line and first-letter also work.
I think this covers everything in
https://www.w3.org/TR/css-pseudo-4/
that is currently supported by blink.
Add WPT tests.
Rename test file since it now covers pseudo elements in general.
Bug: 805271
Change-Id: I16d1df2d18008ee5e080dda7dcebf4d584a4bf3c
Reviewed-on: https://chromium-review.googlesource.com/c/1429779
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625612}
--
wpt-commits: 4f4507f21473c6554d580f4cb60589cf8efcdcf7
wpt-pr: 15011
Automatic update from web-platform-tests
Reland "Switch to new ICE state implementation"
This is a reland of e902e08dc0c67fd7598a4a4e431177f89c00f350
Original change's description:
> Switch to new ICE state implementation
>
> With this change the ice/dtls connection states should finally be compliant to the spec.
>
> Bug: webrtc:6145
> Change-Id: I1e7c13f22e40b534e732ecd3fc103f617306f00a
> Reviewed-on: https://chromium-review.googlesource.com/c/1371392
> Commit-Queue: Jonas Olsson <jonasolsson@chromium.org>
> Reviewed-by: Henrik Boström <hbos@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#617476}
Bug: webrtc:6145
Change-Id: Ie4a09594e8a59c6598a9434c0132c1fd3543c76b
Reviewed-on: https://chromium-review.googlesource.com/c/1433237
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Jonas Olsson <jonasolsson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625611}
--
wpt-commits: e8365d71bf3a36ba494fbc96898d09e48f11e021
wpt-pr: 15038
Automatic update from web-platform-tests
Remove the `./wpt check-stability` command (#15012)
It hasn't been used in Travis CI since https://github.com/web-platform-tests/wpt/pull/14033.
--
wpt-commits: 12527c2a641a1f439a86762c60a47293b6c05272
wpt-pr: 15012
Automatic update from web-platform-tests
[ Feature Policy ] Report for unoptimized-images
This CL adds the logic for reporting potential and actual violations of
the unoptimized-images policy.
Bug: 915788
Change-Id: Ide886ef8d04af0f7a36f63b99be8269cf8d2014d
Reviewed-on: https://chromium-review.googlesource.com/c/1421740
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625588}
--
wpt-commits: fd09bdd65df429534a52c5aaf5107ad518b8dfc0
wpt-pr: 15025
Automatic update from web-platform-tests
CSS: Reject unitless lengths in inset shorthand
Even though the 'top' property accepts unitless lengths when
specified as a longhand, the shorthand 'inset' that sets 'top'
does not allow unitless lengths.
Discussed in
https://github.com/w3c/csswg-drafts/issues/3525
RESOLVED: Do not allow quirks in 'inset' shorthand
BUG: 924691
Change-Id: I53f642e48e8f5d4754aebb70c18d9abc7b7e6248
Reviewed-on: https://chromium-review.googlesource.com/c/1432272
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625584}
--
wpt-commits: 3c6a5979a8dd97fbd5931ae7df4c9e608fada614
wpt-pr: 15027
Automatic update from web-platform-tests
Reland "Add quota usage details tests for all other storage backends."
This is a reland of 548e7b5e622ad79155ff95ef26738d7a40fe9397
Original change's description:
> Add quota usage details tests for all other storage backends.
>
> IndexedDB test was included in parent CL.
>
> Bug: 904000
> Test:
> Change-Id: Icc3462f13d0dce0197a8ec54f22d5ad794a51292
> Reviewed-on: https://chromium-review.googlesource.com/c/1334659
> Reviewed-by: Victor Costan <pwnall@chromium.org>
> Reviewed-by: Joshua Bell <jsbell@chromium.org>
> Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#616398}
Bug: 904000
Change-Id: I507ec17eabc8e323a7c6418075d4be4787d4c5df
Reviewed-on: https://chromium-review.googlesource.com/c/1378805
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617285}
--
wpt-commits: 7e5cdeab733b40357f553704fddddf6c5f199c8b
wpt-pr: 14531
Automatic update from web-platform-tests
Adds getStats() method to RTCQuicTransport.
getStats() returns a promise that resolves with a dictionary of stats
defined in the RTCQuicTransportStats dictionary.
Bug: 874296
Change-Id: I907e529ebf074842c6702df7d90349515c48a5ba
Reviewed-on: https://chromium-review.googlesource.com/c/1430599
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Steve Anton <steveanton@chromium.org>
Commit-Queue: Seth Hampson <shampson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625524}
--
wpt-commits: 72fa242727cb8e3515df9b4af598a43431faa10e
wpt-pr: 15021
Automatic update from web-platform-tests
[LayoutNG] Fix crash related to clearance and margin collapsing.
The root of this bug was that the parent bfc, and child with clearance
were fighting as to what the BFC block offset should be.
The child was always returning true within:
NeedsAbortOnBfcBlockOffsetChange
... as the floats bfc offset was never equal to the child bfc offset,
as the child got affected by clearance.
This fix is to adjust the FloatsBfcBlockOffset by clearance to check
if we need to relayout or not.
Additionally we were performing more layouts than we should be,
when propagating the BFC block offset up the tree upon an abort. We
should be checking if the child got affected by clearance, and if so
adjust the resolved BFC offset accordingly.
Bug: 923271
Change-Id: Id39905a5445a0fe502c16b956b92d6db13885d36
Reviewed-on: https://chromium-review.googlesource.com/c/1423929
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625411}
--
wpt-commits: 66355d4d7ff62616686c39d8b831d2104729993f
wpt-pr: 15003
Automatic update from web-platform-tests
[Azure Pipelines] make the artifact names unique per job (#15019)
This will simplify getting restults from master:
https://github.com/web-platform-tests/wpt.fyi/pull/1054
(The artifact name for all_macOS remains 'results'.)
--
wpt-commits: 71a9dc7cfd4a54f888f7a337730324d494ffa43e
wpt-pr: 15019
Automatic update from web-platform-tests
Snap the snapped_dest_rect for backgrounds
For some reason the snapped_dest_rect for background image geometry
calculations was not actually snapped. Snapping it fixes cases where
we were not filling to the border without regressing any tests (in
fact improving some).
Probably fixes most of the background bugs resulting from the previous
big refactoring.
R=fmalita@chromium.org
BUG=912423,889426
Change-Id: Ieba65130e7f8c0e95db7375ab3a8188bfc78d8d5
Reviewed-on: https://chromium-review.googlesource.com/c/1372556
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#616014}
--
wpt-commits: 6bbf5072ab0f8122c825901547265d88f8b02649
wpt-pr: 14469
Automatic update from web-platform-tests
[WebLocks]: Modifying weblocks algos to be O(1)
The behaviour of the request/release operations of web locks are
modified to be O(1) instead of their currently O(n) worst case runtime.
Additionally the query-order wpt is modified to reflect the new spec
requirement that the state returned by navigator.locks.query need only
respect ordering for requested locks per resource.
Bug: 913014
Change-Id: I819f8c27c995cb698a7c8b2c75ee80d32c744f07
Spec: https://wicg.github.io/web-locks/#algorithms
Reviewed-on: https://chromium-review.googlesource.com/c/1367910
Commit-Queue: Andreas Butler <andreasbutler@google.com>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#621833}
--
wpt-commits: 27085bc4fef9a55a5f5dd530c6e8ff798ff8c6c4
wpt-pr: 14420
autofoolip
Ms2ger
Tsuyoshi Horo
Tab Atkins Jr
Gérard Talbot
Philip Jägenstedt
jimevans
Henrik Skupin
Andreas Butler
Majid Valipour
Javier Fernandez
moz-wptsync-bot
Nicolas Pena
Lukasz Anforowicz
Ian Clelland
Kinuko Yasuda
Rayan Kanso
pyup-bot
John Rummell
Fergal Daly
Jonas Olsson
Ehsan Karamad
Eric Willigers
Jarryd
Seth Hampson
Marcos Cáceres
Ian Kilpatrick
Aleks Totic
Stephen Chenney