Automatic update from web-platform-testsMake IndexedDB/support.js work in workers
This should fix the test
html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/serialization-via-idb.any.worker.html
Part of #11269.
--
wpt-commits: 60a937de7bd20eb1890893a48423a79b096866d8
wpt-pr: 11348
Automatic update from web-platform-testsRedirect POST requests using .py resource
Part of #11269.
Also see #11343.
--
wpt-commits: ec9ffb132d24fa16088b90db12a65509b72ef826
wpt-pr: 11354
Automatic update from web-platform-testsTest for used column-count when column-count/width are not auto (#10250)
--
wpt-commits: 8b089cb6cebe9c83a471e5cfb10a1570dad65ed4
wpt-pr: 10250
Automatic update from web-platform-testsXMLHttpRequest: upload listener flag
Tests for https://github.com/whatwg/xhr/issues/95.
--
wpt-commits: 1706eb31b901d4e5ce8bb873ffb5b31bb01e1e58
wpt-pr: 5122
Automatic update from web-platform-tests[LayoutNG] Need to know when establishing a new FC during min/max calculation.
When we have to lay out an object to determine its min/max inline size,
and the node establishes a new formatting context, we need to create a
constraint space that reflects this. The block size of the float needs
to be included in the block size of its container, because this block
size will be the min/max preferred inline size of the container of that
container, if the writing modes are orthogonal.
Avoid some duplicate code for creating the constraint space builder. The
second builder, the one that redoes layout with infinite available space
now gets SetFloatsBfcOffset() called, which was previously missing, but
that must have been an oversight.
This fixes the recently introduced regression with
fast/multicol/vertical-rl/column-rules.html and also another test.
Wrote a new test that tests exactly what I wanted to fix as well.
Bug: 847807
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I7b28a0ef8061fc3089deb488ad0a78b81776295d
Reviewed-on: https://chromium-review.googlesource.com/1084989
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564438}
--
wpt-commits: aa5ec97282685cba4a2ae34165ddb5043c251e39
wpt-pr: 11330
Automatic update from web-platform-testsHTML: Fix sandbox-disallow-same-origin.html to expect SecurityError
Part of #11269.
--
wpt-commits: e4fd758fb3ed204ec4234eb678323273a99eb685
wpt-pr: 11341
Automatic update from web-platform-testsExperimental Priority Hints support on fetch() API
Adding support for Priority Hints on the fetch() API under an
experimental flag. This adds the notion of importance to core/fetch
code, and adds a new member to the RequestInit dictionary to communicate
developer-specified "importance" downstream.
R=kinuko@chromium.org, kouhei@chromium.org, yhirano@chromium.org, yoav@yoav.ws
Bug: 821464
Change-Id: Ib96a128d77004029e86122c07552250c697dea5f
Reviewed-on: https://chromium-review.googlesource.com/1084063
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
Cr-Commit-Position: refs/heads/master@{#564410}
--
wpt-commits: dae7535c0428fbf057a5c39f324d5a3f47ba64c7
wpt-pr: 11317
Automatic update from web-platform-tests[wptrunner] End Sauce Connect process gracefully (#11334)
Previously, the Sauce Connect process was closed gracefully in response
to prolonged period of inactivity. This procedure was not used under
normal operating conditions.
Factor graceful shutdown logic into a new method, `quit`, and reuse this
method to end the process following successful test completion.
--
wpt-commits: 2bd11b91d490ddd5237bcb6d8149a7f25faaa101
wpt-pr: 11334
Automatic update from web-platform-testsRevert "WaveShaper must output non-zero values even if input is silent"
This reverts commit 325b492fe733ba4c8b2128069a0a232fea1789e3.
Reason for revert: Broke webaudio/.../waveshaper-364379.html in
webkit_layout_tests. See https://crbug.com/849535
Original change's description:
> WaveShaper must output non-zero values even if input is silent
>
> If the curve for the WaveShaperNode is such that a zero input produces
> a non-zero output, the WaveShaperNode needs to output that value even
> if the input is silent (or disconnected).
>
> Do this by setting the tail time of the processor to 0 or infinity
> depending on whether the curve specifies an output value of zero or
> not, respectively.
>
> Bug: 807301
> Test: WaveShaper/silent-inputs.html
> Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b
> Reviewed-on: https://chromium-review.googlesource.com/896266
> Commit-Queue: Raymond Toy <rtoy@chromium.org>
> Reviewed-by: Hongchan Choi <hongchan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#564186}
TBR=rtoy@chromium.org,hongchan@chromium.org
Change-Id: I29fd96b1a9dd2b87db12867031399b069beba706
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 807301, 849535
Reviewed-on: https://chromium-review.googlesource.com/1086647
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564359}
--
wpt-commits: fa5ee47808411c866d09ad6a34dccf383b097bca
wpt-pr: 11338
Automatic update from web-platform-testscustom-elements: Element created by createElement(name, options) with valid custom element name and options set to undefined should be upgraded
createElement('my-element', undefined) was not being upgraded, though both
createElement('my-element') and createElement('my-element', {}) were.
Bug: 841725
Change-Id: Id43b21f8e1cad10745dedf3699691da7ad85cf03
Reviewed-on: https://chromium-review.googlesource.com/1084007
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564352}
--
wpt-commits: 8a5301b16f5e913bf9ffbb7d76abfda9d2435af2
wpt-pr: 11312
Automatic update from web-platform-testsCompute correct sticky box constraints within scrollable containers
Currently calculating the skipped offset between sticky and its
containing block assumes that the latter is not scrollable. However,
when it is we should ignore the scroll offset from the container
otherwise scrolling the container would cause the sticky offset
incorrectly double accumulated.
Bug: 841551
Change-Id: Ib49aaa74808847dcf6fce7dc0db9ac4d2de06c64
Reviewed-on: https://chromium-review.googlesource.com/1054488
Commit-Queue: Yi Gu <yigu@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564276}
--
wpt-commits: dc60bfc45b49e3a5e653320e65b0fd447676b836
wpt-pr: 10958
Automatic update from web-platform-testsMake multiple-workers tests fail if (Shared)Worker is not defined
Fixes#11222.
Part of #11269.
--
wpt-commits: 4f7d09666f738d1db19ba49721b2db4330bf4e82
wpt-pr: 11223
Automatic update from web-platform-testsWaveShaper must output non-zero values even if input is silent
If the curve for the WaveShaperNode is such that a zero input produces
a non-zero output, the WaveShaperNode needs to output that value even
if the input is silent (or disconnected).
Do this by setting the tail time of the processor to 0 or infinity
depending on whether the curve specifies an output value of zero or
not, respectively.
Bug: 807301
Test: WaveShaper/silent-inputs.html
Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b
Reviewed-on: https://chromium-review.googlesource.com/896266
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564186}
--
wpt-commits: 5007510675fa679ff60a44a9d10ae33903fa275c
wpt-pr: 10857
Automatic update from web-platform-testsClarify expectations for failing cookie tests (#8584)
These clean ups are split out from https://crrev.com/c/788217:
- Defining the assert failure messages
Change-Id: I74ba2bb70e907a28292301046a7433480ab669d8
--
wpt-commits: 64f8dcf90b637440e557fc9bd6b11316a3129c18
wpt-pr: 8584
Automatic update from web-platform-testsUpdate git documentation (#11322)
Remove parts that are no longer relevant (we only have one repo now, we
no longer use submodules...), and update graphics.
Related to #5301
--
wpt-commits: 3b8c1c4810dfb47c16016e324321ddeba97c4a15
wpt-pr: 11322
Automatic update from web-platform-testsRemove extra space from '<link rel="reviewer" title="Chris Lilley"'
The following command was applied: sed -i 's/<link rel/<link rel/' *.xht
This matches the current spacing from https://github.com/w3c/woff2-tests
--
Update assert, help, titles to match current ouput of w3c/woff2-tests
--
wpt-commits: cfae5d21db808c41357e4e61aa83ea375fe99809, 018f0589197bfbf9e3adeb0952b097bba94710c2
wpt-pr: 11311
Automatic update from web-platform-testsDo not allow the empty string as a facingMode constraint value for MediaStreams.
The empty string is an invalid facingMode value that was being
interpreted to be equivalent to the internal facing-mode value of NONE.
Bug: 814309
Change-Id: I260fbc41fd17a8bdcd1ca63baffe3bed14f3c4ab
Reviewed-on: https://chromium-review.googlesource.com/1072471
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564046}
--
wpt-commits: 2d0250896ebe871e950ac6c4c8acfa3ec7d5c72d
wpt-pr: 11208
Automatic update from web-platform-tests[css-paint-api] Fail a reftest early if CSS.registerProperty is not supported
Part of #11269.
Also fix remaining instances of CSS.registerProperty
--
wpt-commits: 0b66b59f9d2684e6ac3dc7dd7b5d633c515f22ac
wpt-pr: 11273
Automatic update from web-platform-testsAdd a WPT for Service-Worker header
The spec requires that an HTTP request to fetch a service worker
script has 'Service-Worker: script' header[1].
[1] https://w3c.github.io/ServiceWorker/#update-algorithm
Bug: 848265
Change-Id: I76c836fcf43d287bcac910c3655e5b127ad8555c
Reviewed-on: https://chromium-review.googlesource.com/1082253
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564023}
--
wpt-commits: 6ed8b9045489f5d5fd00da465c3cd1df443787be
wpt-pr: 11290
Automatic update from web-platform-testsAdd filtering support to ManifestLoader.
In some use cases, the overhead of creating data structures for all tests in
the manifest, and then filtering them, is too big. This change allows users
to filter tests when initially creating the manifest.
--
wpt-commits: f1815a9219ee5ec7fe27ef7a5cfb3fa00b8485c7
wpt-pr: 11306
Automatic update from web-platform-testsPaymentHandler: Fix a crash when creating event object with empty data
The following codes cause crashes in current implementation.
- new CanMakePaymentEvent("canmakepaymentevent", {});
- new PaymentRequestEvent("paymentrequestevent", {});
This patch fixes the problem and fixes/adds WPT tests.
Bug: none
Change-Id: I95375f1148d69a17075d393990e3726ad2bf1cf3
Reviewed-on: https://chromium-review.googlesource.com/1070957
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563903}
--
wpt-commits: 1dc612f2ed6a6bec861a90ad9bfa9a4336165dcd
wpt-pr: 11146
Automatic update from web-platform-testsRevert "Cleanup plugin element frames when the layout tree is detached"
This reverts commit 596e6b3281a8cc2c4b646553e4cde169a29a1d1d.
Reason for revert: DetachLayoutTree could be called at inopportune times
such as style recalc or during layout. This caused several crashes.
Original change's description:
> Cleanup plugin element frames when the layout tree is detached
>
> Unlike frames, plugin elements (<embed> and <object>) are updated
> when their layout tree is rebuilt. However, due to an oversight,
> <embed> or <object> elements displaying subframes would only have
> the associated content view (FrameView) torn down, leaving a
> dangling content frame.
>
> This led to some interesting side effects:
> - When transitioning from a local frame to a plugin, the content
> frame would remain live, with JS still happily running.
> - When transitioning from a remote frame to a plugin,
> - When navigating a remote frame from one URL to another, the
> element would stop updating since the FrameView would be torn
> down but a new one would never be created. Note that this was
> not (as much of) a problem for local frames, since local frames
> re-create the LocalFrameView on every navigation.
> With this CL, if a plugin element has an associated content frame,
> use that to clean up the state associated with the element when the
> layout tree is detached. This can cause the browser context to be
> re-created: this matches the behavior of Edge and Firefox.
>
> Note that there is still one edge case where Blink behaves oddly:
> if the navigation fails and should display fallback content, the
> content frame still remains attached. This will be addressed in
> followups.
>
> Link to whatwg issue: https://github.com/whatwg/html/issues/3576
>
> Bug: 776510, 781880
> Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
> Change-Id: Id18605fbe602ea6c0076c1d579345cdcf28cc984
> Reviewed-on: https://chromium-review.googlesource.com/996314
> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#561768}
TBR=dcheng@chromium.org,creis@chromium.org,alexmos@chromium.org,ekaramad@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 776510, 781880, 847216, 846708
Change-Id: I762631b92463352bea9bf3102d90a13b72776786
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Reviewed-on: https://chromium-review.googlesource.com/1083500
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563902}
--
wpt-commits: 69a48d90cac792566f14d734d2bae4feda462829
wpt-pr: 11309
Automatic update from web-platform-testsHTML: Don't confuse test runner by including testharness.js in a popup
Part of #11269.
--
wpt-commits: dcc00e1d0f88a98e30b75cc31d44be6cdfea0ae1
wpt-pr: 11303
Automatic update from web-platform-testsMake dynamic-import tests fail early instead of time out
Part of #11269.
--
wpt-commits: 04cea7f3ce951cf78542e9dfd8621b35ff4c284e
wpt-pr: 11302
Automatic update from web-platform-tests[mediacapture] Simply test and use standard API
The MediaStream's `active` event was removed from the specification in
December of 2015 [1]. The `addtrack` event offers similar semantics, and
as a standard API, it is expected to be implemented by all browsers
which follow the specification. In addition, because it does not depend
on media playback, its use allows `MediaElement#play` to be removed.
That removal simplifies the process of executing the test because
browsers are beginning to tighten their policies regarding automated
media playback [2].
[1] https://github.com/w3c/mediacapture-main/pull/291
[2] https://developers.google.com/web/updates/2017/09/autoplay-policy-changes
--
fixup! [mediacapture] Simply test and use standard API
--
wpt-commits: d2a2ea62ec000ff6d5c1572ba62a089eeb69e0c4, 135d656fb17b99a9bf0e91667b8036b80f2c4d65
wpt-pr: 11211
Automatic update from web-platform-tests[css-layout-api] Adds passing of LayoutConstraints#fixedBlockSize.
This passes a fixed block size constraint into the layout function if:
- It has a fixed/percentage/calc block-size.
- The abs-pos constraints will make a fixed block size.
- It is a quirky body/document (which stretches to fit the viewport).
- It has a fixed block-size constraint from a parent layout.
The tests all behave the same way. The layout which we are interested
in testing looks at the received fixedBlockSize, and if correct performs
layout on the only child with a 100x100 fixed size.
Bug: 726125
Change-Id: I4eec86a843d58a791c9df071e16b71bf2f5d80ee
Reviewed-on: https://chromium-review.googlesource.com/1073636
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563668}
--
wpt-commits: ff4d0553835102b2f68c7bf8dafb205bd3cacb89
wpt-pr: 11260
Automatic update from web-platform-testsMove add_dependency_idls after add_idls (#11305)
Per #11280, the order in which you call these methods matters to execution. Flip the order in order to prevent `Unrecognized type EventHandler`.
--
wpt-commits: 197cdad0521ac04c0057b45ec92ddb3bca68ae19
wpt-pr: 11305
Automatic update from web-platform-testsHTML: split out navigation tests for URL query-encoding tests
Part of #11269 and #4934.
--
wpt-commits: 596c572f97a886dc7d8a3239737d42af161d4d9d
wpt-pr: 11300
Simon Pieters
David H
Geoffrey Sneddon
Manuel Rego Casasnovas
Anne van Kesteren
moz-wptsync-bot
Morten Stenshorne
Dominic Farolino
jugglinmike
Matt Giuca
Justin Ribeiro
Yi Gu
Raymond Toy
youennf
joanmarie
Blink WPT Bot
Florian Rivoal
Frédéric Wang
Ms2ger
Guido Urdaneta
Kenichi Ishibashi
Michael[tm] Smith
Jinho Bang
Ehsan Karamad
François REMY
Ian Kilpatrick
Chris Nardi