Automatic update from web-platform-testsSnap at ScrollIntoView.
According to the spec,
https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-386154394
scrollIntoView should
1) Always snap to the target element's snap alignment, and
2) All the affected scrollers should also land on a snap position if
one exists.
This patch does part 2). Before a scrollable_area is added to
the smoothScrollSequencer with its new scroll_offset, we will check if
it has a valid snap offset around, and update the final offset
accordingly.
We'll implement part 1) in a separate patch.
Bug: 842317
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ica22134ed0b1f9d36f5a017c8dd0be54e907dd3d
Reviewed-on: https://chromium-review.googlesource.com/c/1188746
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607019}
--
wpt-commits: a0610cf468e6208e74b2cfda77a565ab90fbd74e
wpt-pr: 13038
Automatic update from web-platform-testsgrid-template-areas serialization
strings in grid-template-areas are normalized, e.g. collapsing
whitespace to a single space, and collapsing repeated periods ('.')
to a single period.
https://github.com/w3c/csswg-drafts/issues/3261#issuecomment-436828363
--
Merge pull request #13977 from ewilligers/grid-template-areas-serialization-2
grid-template-areas serialization
--
wpt-commits: da90a07f543e3307b53230a1f0a2e8b6dc72b42b, a27659a86371bb2d98e622f4e57b85a546898ade
wpt-pr: 13977
Automatic update from web-platform-testsNEL: Generate reports in HTTPNetworkTransaction
Piece by piece, we are moving the Reporting and NEL processing code from
URLRequest and friends into HTTPNetworkTransaction, to make sure that we
produce reports for network requests as defined by the spec.
This patch moves the generation of the actual NEL reports, and includes
some new WPT test cases that verify that we create reports correctly for
redirects and cached responses.
TBR=msramek@chromium.org
Bug: 895823
Change-Id: Ie8e17a2a2b3571a7cdfd39057da486f5ad2c9f6f
Reviewed-on: https://chromium-review.googlesource.com/c/1318169
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Reviewed-by: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606958}
--
wpt-commits: 9902fbae9124fb565389983e49235d82cf429242
wpt-pr: 14007
Automatic update from web-platform-testsbrowser.py code cleanup
Some code cleanup that was recommended in https://github.com/web-platform-tests/wpt/pull/13185
--
wpt-commits: 7c568fdbd98ccdb92152c14521d3cc8c729a45a2
wpt-pr: 13239
Automatic update from web-platform-testsAdd a wpt create command
wpt create makes a file with the required elements for a test, and
optionally opens it in an editor.
--
wpt-commits: 726725be8f98607d521632e595fe5f2054570158
wpt-pr: 13701
Automatic update from web-platform-testswebkitRelativePath preserves common ancestors (#13988)
Drop requirement that webkitRelativePath only provides the shortest common ancestor, which matches behavior in Edge/Safari/Firefox, and soon Chrome.
Spec change: e6b848f4dc
Tracking issue: WICG/entries-api#18
--
wpt-commits: 378b79a9cd09df75403d88828d1793bb720a9488
wpt-pr: 13988
Automatic update from web-platform-testsWire the resizeMode property to the constraints parsing mechanism.
This CL adds resizeMode support for MediaStreamTrack.getConstraints()
and marks resizeMode as a supported constrainable property.
Support for getUserMedia(), applyConstraints() and getCapabilities()
will be added in follow-up CLs in this series.
Intent to Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/V2srjdzRCXE
Bug: 854980
Change-Id: Ia23b8119768ab67ab498f0f8e2267aeb388f9fc3
Reviewed-on: https://chromium-review.googlesource.com/c/1309749
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606856}
--
wpt-commits: 055077093043d235040d20ae60458ee5ac6cded5
wpt-pr: 13846
Automatic update from web-platform-testsSetup logging earlier in the wpt run startup.
Curerntly we wait until we're setting up wptrunner kwargs to create the logger.
But that's pretty silly; we should set up the logger first thing and then use it
consistently to log during the setup phase.
--
wpt-commits: 47f0061f15dd2973dab11d87c03f0c8264d32e02
wpt-pr: 13578
Automatic update from web-platform-testsDo not send old capabilities to ChromeDriver
The configuration for Chrome currently sends 'platform' and 'version'
capabilities to ChromeDriver. These capabilities are non-standard and
unnecessary, and will cause errors when ChromeDriver becomes more
standard compliant.
--
wpt-commits: 7d9070444977a83af886d73bf80d57096be70ca5
wpt-pr: 13995
Automatic update from web-platform-testsFetch: CORS and request's Content-Type header
For https://github.com/whatwg/fetch/pull/829.
--
wpt-commits: eed621bc2f995bced9481df2cead4c4632c72cdd
wpt-pr: 13921
Automatic update from web-platform-testshtml: Fix a sanitization issue of type-change-state.html
type-change-state.html assumed sanitized value for " foo\rbar " was
fixed per a input type, and it was specified by 'sanitizedValue' field.
However, it depends on the previous type. For example, the new input
types of the following A and B are same, initial value setter arguments
are same, but sanitized values of A and B should be different due to the
sanitizer difference between 'hidden' and 'url':
A)
input.type = "hidden";
input.value = " foo\rbar ";
// input.value is " foo\rbar "
input.type = "text";
// input.value is " foobar ".
B)
input.type = "url";
input.value = " foo\rbar ";
// input.value is "foobar"
input.type = "text";
// input.value is "foobar".
This CL fixes this issue by replacing 'sanitizedValue' field with
'sanitizer' field, which specifies a simple sanitizer implementation.
This fixes five test cases, which have failed with all major browsers.
Change-Id: I1b5f75e610138b1d117e93723471427ee655c300
Reviewed-on: https://chromium-review.googlesource.com/c/1326203
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606730}
--
wpt-commits: 3cd60908e05beed166359907018c2abe238cb205
wpt-pr: 13993
Automatic update from web-platform-tests[media] Treat cross-origin redirect as TAINTED only for no-cors requests
With https://crrev.com/a9cbaa7a40e2b2723cfc2f266c42f4980038a949,
WebMediaPlayer blindly treats a resource experiencing cross-origin
redirects as TAINTED. In fact, it should be treated as TAINTED only
when its request mode is "no-cors".
The added tests are provided by hongchan@chromium.org.
Bug: 899745, 901383
Change-Id: Idb66407552085b053818f3e4a9d8d5ff3ddeaf45
Reviewed-on: https://chromium-review.googlesource.com/c/1325281
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Fredrik Hubinette <hubbe@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606681}
--
wpt-commits: d5be80a86d4f938250c075ac12414ad47516969c
wpt-pr: 13980
Automatic update from web-platform-testsReland "Make XR FrameData and Environment mojo associated"
This is a reland of 126a1168e3bcffb43c706822b3aa28695840310f
The fix in this change addresses compile errors on the
Oculus platform.
TBR=dcheng@chromium.org
dcheng@chromium.org: please review, though there are no
new changes to vr_service.mojom
Original change's description:
> Make XR FrameData and Environment mojo associated
>
> The XRFrameDataProvider now returns an associated
> XREnvironmentDataProvider interface so that the
> two share callback queues and thus allow strict
> ordering of the two interfaces. This is critical
> for frame synchronization between frames and the
> associated environment data.
>
> Note: We can't just mark the interfaceptrs for
> XRFrameDataProvider and
> XREnvironmentIntegrationProvider as associated
> in the XRSession struct. XRDevice implementations
> mostly live on separate threads from the
> XRFrameDataProviders, so we'd have extra thread
> hopping. For the VR headsets we explicitly live
> off the main thread to avoid latency, and because
> we do some work that may block the thread the
> XRFrameDataProvider lives on (for example waiting
> for vsync, or submitting frames to headset APIs).
>
> Bug: 867057, 876135, 843376
> Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
> Reviewed-on: https://chromium-review.googlesource.com/c/1171794
> Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Bill Orr <billorr@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605545}
Bug: 867057, 876135, 843376
Change-Id: If76578ebabbb40d03a21f6f557c5d4c27f69fc38
Reviewed-on: https://chromium-review.googlesource.com/c/1324089
Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606643}
--
wpt-commits: a516e7edca11e2efe462d2bfc83b5b88dd9f4072
wpt-pr: 13969
Automatic update from web-platform-testsThe computed value of float with absolute positioning when there is no box should be "none" (#13958)
https://github.com/w3c/csswg-drafts/issues/1436
--
wpt-commits: 4477b9d2fadaca4314a9fc7d88ab6db6ad47a321
wpt-pr: 13958
Automatic update from web-platform-testshtml: Fix an issue of type-change-state.html about selectionDirection="none"
type-change-state.html contains assertions for the following operation in [1]:
> ..., and set its selection direction to "none".
However it had an issue that the assertions checked if
input.selectionDirection was "none". According to [2],
input.selectionDirection can be "forward" on specific platforms.
> update the element's selection direction to the given direction, unless
> the direction is "none" and the platform does not support that direction;
> in that case, update the element's selection direction to "forward".
[1] https://html.spec.whatwg.org/multipage/input.html#the-input-element:set-the-selection-direction
[2] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#set-the-selection-direction
Change-Id: Idc1a97fbb2036e351a788a1f758b3239308d8c71
Reviewed-on: https://chromium-review.googlesource.com/c/1322264
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606310}
--
wpt-commits: 603b17f321fe4275050c59c87b1f3a29a33e9c96
wpt-pr: 13978
Automatic update from web-platform-tests[streams] Add tests for aborting pipeTo()
Add tests for aborting ReadableStream.prototype.pipeTo using an
AbortSignal.
Tests correspond to PR whatwg/streams#744.
--
wpt-commits: 349d41838068164e37a1cbd1c8c6ffeba4c72177
wpt-pr: 13358
Automatic update from web-platform-testsWindow onerror is not triggered bug fix
As pointed out in the bug, unhandled errors on worker threads were not
properly being propagated for the parent thread to handle as the spec
requires (https://html.spec.whatwg.org/multipage/workers.html#runtime-script-errors-2).
This fix adds in the code to do that.
Bug: 685303
Change-Id: Ie3e7ec03153a43efdc6e70b874d6b1a1d8ac35ef
Reviewed-on: https://chromium-review.googlesource.com/c/1287208
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605857}
--
wpt-commits: 920e3b1051f7bcb1fff98417cf91c904dbbdd36a
wpt-pr: 13691
Automatic update from web-platform-testswebkit: add support for the WPE port (#13863)
WPE port is closely related to the GTK port, using the same WebDriver
implementation as well as similar testing-purpose browser application.
Much of the capabilities dictionary construction can thus be the same.
--
wpt-commits: 89692eac0360247e56ba1ae4c32ea38cf1b6a9a0
wpt-pr: 13863
Automatic update from web-platform-testsEnsure that lone surrogates don't appear in wptreport json (#13828)
Python will happily handle "string" data containing codepoints in the surrogate
range. In the JSON output these are always escaped and appear as \uD800 or
similar. That's pretty unfortunate for interop since other languages don't
necessarily support such codepoints not representing a character in the
unicode set in their normal string type. Although it's possible to clean this
up on import it seems more reasonable to ensure that our primary interchange
format is unicode-clean. Therefore this change starts escaping lone surrogates
using the U+ notation so that \uD800 becomed U+D800.
Because Python, this requires two implementations. In UCS4 Python we know that
only lone surrogates should appear in string data; characters outside the BMP
will be represented as a single internal character (*technically* this is
untrue since someone may manually create a string containing a sequence of
surrogates that happens to form a pair; we don't care about handling this
case other than as two unpaired surrogates that happen to be adjacent). In
UCS2 Python surrogates appear in the string data literally, so we need to
check each time we encounter one whether it's a low surrogate followed by
a high surrogate and not escape in that case.
--
wpt-commits: 275904c8b770d10a9d67f6786b75dd4461a9a932
wpt-pr: 13828
Automatic update from web-platform-testsupdate wpt feature policy tests, making them long tests
Bug: 829921
Change-Id: Ia2c70c62d4a4235b21996bbd185746080e1efa35
Reviewed-on: https://chromium-review.googlesource.com/c/1320010
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606045}
--
wpt-commits: 1a7cb3deb6c8661e4cf245a7ffc3e324fb6795f2
wpt-pr: 13954
Automatic update from web-platform-testswebkit: provide port name as run info (#13862)
For the WebKit product, include the port name inside the run info, under the
'webkit_port' key. This will come in handy when disabling tests in metadata files
for specific ports.
--
wpt-commits: 9b9cf22d132ce60af8ad1801fd347965a1a96bae
wpt-pr: 13862
Automatic update from web-platform-tests[ci] Complete Docker image update (#13960)
A recent patch updated the Docker image used by Taskcluster when
building the project's `master` branch [1]. Update the corresponding
configuration for tasks triggered by pull requests. This improves parity
between the two processes, and because the new image is based on a more
recent LTS release of Ubuntu, it reduces the likelihood of errors due to
outdated system dependencies.
[1] https://github.com/web-platform-tests/wpt/pull/13676
--
wpt-commits: 3b729257c88fc09f200993317b6b84c9ae0aee3b
wpt-pr: 13960
