Automatic update from web-platform-tests[Blobs] Correctly set mimetype of blob in FetchDataLoader.
Just creating a new BlobDataHandle doesn't actually update the mimetype
of the blob (if later the blob is requested through a blob: URL for
example), so instead actually create a new blob wrapping the existing
blob to properly change the mimetype.
Bug: none
Change-Id: I93b6d584178a02a74d68bdd6fcace1514ca90ec0
Reviewed-on: https://chromium-review.googlesource.com/967271
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544864}
wpt-commits: 3c0e03dcd57325686f7ce4b660ba0e2cdc3dd35f
wpt-pr: 10101
wpt-commits: 3c0e03dcd57325686f7ce4b660ba0e2cdc3dd35f
wpt-pr: 10101
Automatic update from web-platform-testsTest that DTMFSender rejects properly after close
This verifies that the sender throws the right error
when called after the connection closing.
Bug: chromium:822799
Change-Id: Id3ab4ddc65b1510526fa49b7bfe3f9f95a7f2d65
Reviewed-on: https://chromium-review.googlesource.com/968927
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544804}
wpt-commits: b1ef882561da6110852ba6f96f2043a24d00dcb7
wpt-pr: 10109
wpt-commits: b1ef882561da6110852ba6f96f2043a24d00dcb7
wpt-pr: 10109
Automatic update from web-platform-testsImplement scroll-snap-type: proximity
As specified in the spec, when the snap-container has scroll-snap-type:
proximity, we should only consider snap positions that are close to the
current scroll offset.
https://drafts.csswg.org/css-scroll-snap-1/#snap-strictness
Bug: 823820
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I6312f98df421e303eb538f422ede39cea8dd5d38
Reviewed-on: https://chromium-review.googlesource.com/971466
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Reviewed-by: Ali Juma <ajuma@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544783}
wpt-commits: c6ed7397bed7c2df7b6033bc6c6f6dc24bb0a32e
wpt-pr: 10115
wpt-commits: c6ed7397bed7c2df7b6033bc6c6f6dc24bb0a32e
wpt-pr: 10115
Automatic update from web-platform-tests[css-grid] Fix testing-utils.js
We have been calling testGridTemplateColumnsRows() with
and without arrays.
Arrays are needed because the serialization of 2 tracks of the same size
can be "100px 100px" or "repeat(2, 100px)".
But in the rest of the cases we don't need an array,
so we call the method with a single value.
testGridTemplateColumnsRows() was not ready to support that,
and it wasn't actually checking anything in that case.
The patch modifies testing-utils.js, so it wraps values in an array
when required.
Now testGridTemplateColumnsRows() will be actually checking things.
Change-Id: I7e360677c391df74dedb474922bf5c04247141c5
Reviewed-on: https://chromium-review.googlesource.com/973063
Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#544681}
wpt-commits: 535e9629904e3f24ac891763d5d24b8475df5926
wpt-pr: 10122
wpt-commits: 535e9629904e3f24ac891763d5d24b8475df5926
wpt-pr: 10122
Automatic update from web-platform-testsAttempt to fix ci_resources_unittest (#10116)
The test wasn't running against the downloaded Firefox Nightly but
system Firefox instead, which is fixed by passing the binary path to
tox (which then passes it to pytest conftest.py).
The pip requirements should be managed by tox.
wpt-commits: 47c9322f474fe123c6df2223bd93b8fd0056c6f9
wpt-pr: 10116
wpt-commits: 47c9322f474fe123c6df2223bd93b8fd0056c6f9
wpt-pr: 10116
Automatic update from web-platform-testsuser activation must survive postMessage() to call show() (#10090)
Check that we can call pr.show() in an iframe via postMessage(), which is triggered by user activation.
wpt-commits: 92885acfbbfa2ad0fe08310857379cb4c84797c0
wpt-pr: 10090
wpt-commits: 92885acfbbfa2ad0fe08310857379cb4c84797c0
wpt-pr: 10090
Automatic update from web-platform-testsExit check_stability with an error when no tests run
Similar to #10030 (which was for `wpt run`), this commit makes `wpt
check-stability` return a non-zero exit code when no tests run.
Also fix some code smells:
* `run` was redefined by `do_delayed_imports` to a different function.
Rename the other `run` method in this module to `setup_and_run`.
* `retcode` was unnecessarily defined in the top scope. Remove it to
avoid redefinition.
* `global logger` and the call to `get_parser` were extraneous in `run`
(now `setup_and_run`) and hence are removed.
--
Address comments
* Renaming `check_stability.run` breaks commands.json and naming
conventions, so rename the other `run` in that module instead.
* Only return errors for empty results when we know for sure tests are
affected.
wpt-commits: 7e214e852492e619254c14c351a85ac97661d847, 3a8328470d53c4501e31cec2775c4d33821c2275
wpt-pr: 10098
wpt-commits: 7e214e852492e619254c14c351a85ac97661d847, 3a8328470d53c4501e31cec2775c4d33821c2275
wpt-pr: 10098
Automatic update from web-platform-testsNo longer allow Chrome stability check to fail
After #10064, Chrome jobs run successfully on Travis, so we can turn the
stability check back on.
Fixes#9932.
wpt-commits: 4d10320c4970e1d8f3f64aac9fecde03ee0ae87e
wpt-pr: 10082
wpt-commits: 4d10320c4970e1d8f3f64aac9fecde03ee0ae87e
wpt-pr: 10082
Automatic update from web-platform-testsIndexed DB: Consolidate window/worker IDL tests into any.js
Also, rely on HTML and DOM interfaces for dependencies rather
than inline definitions for Event, EventTarget, etc.
Change-Id: I58ac6515f8d2769aec6bbf1b90d9a4105639ad24
Reviewed-on: https://chromium-review.googlesource.com/965452
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544429}
wpt-commits: dacfb4465c26ab8ee6e1e618671b38905b50c02e
wpt-pr: 10063
wpt-commits: dacfb4465c26ab8ee6e1e618671b38905b50c02e
wpt-pr: 10063
Automatic update from web-platform-testsReadableStream: Readable byte stream must call pull if needed after receiving new chunk (#10018)
* Fix test that allows too much pulling
* Test that byte stream pulls after enqueue
wpt-commits: 6e1b5f44943705380487dc73b96b4c959487ee4d
wpt-pr: 10018
wpt-commits: 6e1b5f44943705380487dc73b96b4c959487ee4d
wpt-pr: 10018
Automatic update from web-platform-testsCorrectly reject in-progress body methods with AbortError
Prior to this change, response body methods such as
response.body.arrayBuffer() would reject with a TypeError if the fetch
was aborted. This change makes them correctly reject with an AbortError
instead.
This implements stage #3 of the "Body Cancellation" section of the
design doc:
https://docs.google.com/document/d/1OuoCG2uiijbAwbCw9jaS7tHEO0LBO_4gMNio1ox0qlY/edit#heading=h.fvc7d7q07oio
Bug: 817687
Change-Id: Ifde322d9c22485a8ba9d14fd4ffca65c4fb4745a
Reviewed-on: https://chromium-review.googlesource.com/954765
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544335}
wpt-commits: f2ae7641fad03150b4238a8b34dc9bdfdf58c0dd
wpt-pr: 10096
wpt-commits: f2ae7641fad03150b4238a8b34dc9bdfdf58c0dd
wpt-pr: 10096
Automatic update from web-platform-tests[css-typed-om] support pointer-events property
pointer-events[1] are added to support in whitelist.
there are some camelcase keywords in pointer-events.
actually pre-defined keywords are interpreted
ASCII case-insensitively[2].
so it was changed to accept camelcase keyword in tests.
and test file are also added.
[1]https://svgwg.org/svg2-draft/interact.html#PointerEventsProperty
[2]https://drafts.csswg.org/css-values-4/#keywords
Bug: 820299
Change-Id: Iccc0f88a69bbec68964ef55bcc5c471fea765ccf
Reviewed-on: https://chromium-review.googlesource.com/968581
Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Hwanseung Lee <hwanseung@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544232}
wpt-commits: 234faac690ec3bc8bebd39ae9b2e2b3a3b05ef82
wpt-pr: 10102
wpt-commits: 234faac690ec3bc8bebd39ae9b2e2b3a3b05ef82
wpt-pr: 10102
Automatic update from web-platform-testsWeb Platform Tests: add /interfaces/webaudio.idl and corresponding test
The Web Audio tests (in /webaudio) have idlharness test on an
interface-by-interface basis, but the new hotness is to have the
IDL fragments consolidated. This also allows dependent specs to
include the master interface definitions.
Bug: 679813,697123,785409,823431
Change-Id: I60bc8415627b8b3f43c13060e4bf65f47bc17c2b
Reviewed-on: https://chromium-review.googlesource.com/965401
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544173}
wpt-commits: 3ec34e5a2c8cbeeb7fad521cce0daf923b272a92
wpt-pr: 10062
wpt-commits: 3ec34e5a2c8cbeeb7fad521cce0daf923b272a92
wpt-pr: 10062
Automatic update from web-platform-testsscroll-snap-align should specify inline and block.
Currently, we parse the two values in scroll-snap-align for x and y.
However, according to the spec,
https://drafts.csswg.org/css-scroll-snap-1/#scroll-snap-align, the two
values specify the alignment in the inline axis and block axis. This
patch renames the two values and handles the vertical writing mode for
inline and block alignments.
Bug: 821645
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I78acff0df4698b3f9c0f7443e61e3bad75379b14
Reviewed-on: https://chromium-review.googlesource.com/967890
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Ali Juma <ajuma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544055}
wpt-commits: 26677578ecdfe1c498824f2711f2211d75a0fa71
wpt-pr: 10093
wpt-commits: 26677578ecdfe1c498824f2711f2211d75a0fa71
wpt-pr: 10093
Automatic update from web-platform-testsRemove dependency on external server for background-attachment-004 (#10092)
wpt-commits: 5bb0c8321fd284fa76d8e3e00e6c97de453ee1b5
wpt-pr: 10092
wpt-commits: 5bb0c8321fd284fa76d8e3e00e6c97de453ee1b5
wpt-pr: 10092
Automatic update from web-platform-testsFix sizing of orthogonal elements with percentage margins
LayoutBox::FillAvailableMeasure() was not considering the case of
orthogonal elements when computing the margins.
The margins ended up being properly calculated but the size of
the orthogonal elements was wrong, as they considered
to have more or less space than the available one.
The method is modified in order to use
the containing block inline size in order to resolve the percentages:
https://www.w3.org/TR/css-writing-modes-3/#dimension-mapping
BUG=808758
TEST=external/wpt/css/css-writing-modes/sizing-orthogonal-percentage-margin-00*.html
Change-Id: Ib8c81dcd14589b3fefe806de3f8f75c000b1cac9
Reviewed-on: https://chromium-review.googlesource.com/968522
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544047}
wpt-commits: 69cee83aeab7142e282fc2350846e677b5aebe08
wpt-pr: 10091
wpt-commits: 69cee83aeab7142e282fc2350846e677b5aebe08
wpt-pr: 10091
Automatic update from web-platform-testsFix a typo in a resource file name (#9986) (#10077)
wpt-commits: 5dee619315f5803008443f9bc51536e6be890e5c
wpt-pr: 10077
wpt-commits: 5dee619315f5803008443f9bc51536e6be890e5c
wpt-pr: 10077
Automatic update from web-platform-testsImprove wpt testing on OffscreenCanvas convertToBlob
Same as canvas.toBlob(), the OffscreenCanvas.convertToBlob() are running on
idle tasks by default. When idle tasks do not begin for a long time, they force
encoding on the current thread. As idle tasks are not enabled on layout tests
unless "--enable-threaded-compositing" flag is turned on, we therefore do both
virtual and non-virtual tests to ensure complete test coverage of both
execution paths--idle-task mode and force-encoding mode. The non-virtual tests
need to be marked as [Slow] as the CanvasAsyncBlobCreator is waiting for the
idle tasks for a threshold time before switching to force-encoding mode.
Bug: 817091
Change-Id: I2c7da9e27ee2d24e1a5e6ee1c36597b46f052aca
Reviewed-on: https://chromium-review.googlesource.com/964395
Reviewed-by: Justin Novosad <junov@chromium.org>
Commit-Queue: Olivia Lai <xlai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544036}
wpt-commits: 919015df88121d50623584f5dd02986721dbc3ab
wpt-pr: 10051
wpt-commits: 919015df88121d50623584f5dd02986721dbc3ab
wpt-pr: 10051
--HG--
rename : testing/web-platform/tests/offscreen-canvas/the-offscreen-canvas/offscreencanvas.convert.to.blob.html => testing/web-platform/tests/offscreen-canvas/convert-to-blob/offscreencanvas.convert.to.blob.html
rename : testing/web-platform/tests/offscreen-canvas/the-offscreen-canvas/offscreencanvas.convert.to.blob.w.html => testing/web-platform/tests/offscreen-canvas/convert-to-blob/offscreencanvas.convert.to.blob.w.html
Automatic update from web-platform-tests[css-typed-om] Add support for min/max-width/height.
Add support & tests for (min/max)-(width/height).
Note that the typed om spec specifies the old specs for these properties:
https://drafts.csswg.org/css21/visudet.html
Bug: 820299
Change-Id: I9c65f7f24d84b83ea2e2f167f8fb86be967eff06
Reviewed-on: https://chromium-review.googlesource.com/968003
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543980}
wpt-commits: 918f9684ec3846ac5bf588678dbdde6d58e22fc8
wpt-pr: 10087
wpt-commits: 918f9684ec3846ac5bf588678dbdde6d58e22fc8
wpt-pr: 10087
Automatic update from web-platform-tests[css-typed-om] Add support for motion path properties.
This patch adds support for motion path properties. We had to modify
the computed style computation for <position> values. Previously, we
parse a <position> value as a CSSValuePair, but compute them to a
CSSValueList containing two items. This is very strange, so we just
compute to a CSSValuePair. Since both serialize to the same string,
this has no behavioural changes on CSSOM.
Bug: 820299
Change-Id: I2131055dad0785eb47ea2d2d89f00229f4376bae
Reviewed-on: https://chromium-review.googlesource.com/967915
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543975}
wpt-commits: 1f80be4604d9c5d3f68caa6221080027435f4002
wpt-pr: 10086
wpt-commits: 1f80be4604d9c5d3f68caa6221080027435f4002
wpt-pr: 10086
Automatic update from web-platform-testsFetch: add used body replacement test for Request constructor
See Fetch change https://github.com/whatwg/fetch/pull/675.
Specifically, that PR allows Requests with disturbed bodies to be used as the first parameter to the Request constructor, as long as the RequestInit dictionary contains a body member with which to replace the used body.
As of this writing, no browser implements this change.
wpt-commits: e87f38097902e16348d4e17f4fe3bc2d0112bff1
wpt-pr: 9931
wpt-commits: e87f38097902e16348d4e17f4fe3bc2d0112bff1
wpt-pr: 9931
Automatic update from web-platform-testsbluetooth: FakeBluetoothChooser stub impl.
This change adds a new FakeBluetoothChooser interface stub to expand on.
The design for this class is detailed in the following document:
https://docs.google.com/document/d/1XFl_4ZAgO8ddM6U53A9AfUuZeWgJnlYD5wtbXqEpzeg
BUG=719827
Change-Id: I34169ce62dd5b35796639b7643d899b8315cc4c7
Reviewed-on: https://chromium-review.googlesource.com/909726
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Conley Owens <cco3@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543479}
wpt-commits: ecd2c46c1a10a0c39dd83bcbe2fec5ece4fb6e26
wpt-pr: 9463
wpt-commits: ecd2c46c1a10a0c39dd83bcbe2fec5ece4fb6e26
wpt-pr: 9463
Automatic update from web-platform-tests[shapes] Remove shape-outside avoiding behaviour for new-FCs/replaced.
See intent: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/pfDg-VAeKWs
This makes new formatting contexts behave exactly like floats would
when they are positioned. I.e. they don't look at the shape-outside
of the float, and instead as positioned for their margin box.
I've added a .tentative test as per the intent.
This will allow us to have a (relatively) simple implementation of
css-shapes in LayoutNG as we only have to consider the shape area for
line-boxes. \o/
Bug: 820520
Change-Id: Ib07600a291eb4838675a9a1068c5fc16cac0633f
Reviewed-on: https://chromium-review.googlesource.com/739961
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543813}
wpt-commits: 53ea2c3d98e4da95a50b381c1b44839c47075cf6
wpt-pr: 10057
wpt-commits: 53ea2c3d98e4da95a50b381c1b44839c47075cf6
wpt-pr: 10057
