Bug 1504087 [wpt PR 13846] - Update wpt metadata, a=testonly wpt-pr: 13846 wpt-type: metadata

Bug 1504087 [wpt PR 13846] - Wire the resizeMode property to the constraints parsing mechanism., a=testonly 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

Bug 1506181 [wpt PR 14006] - Fixup logging in stability checks , a=testonly Automatic update from web-platform-testsFixup logging in stability checks -- wpt-commits: bc002a53c26d392cb6ecf23cc0e62ab7cbe46e5c wpt-pr: 14006

Bug 1504402 [wpt PR 13878] - Update wpt metadata, a=testonly wpt-pr: 13878 wpt-type: metadata

Bug 1504402 [wpt PR 13878] - Count partial mixins as tested deps, a=testonly Automatic update from web-platform-testsCount partial mixins as tested deps (#13878) -- wpt-commits: 4176e9ef5f720910505d3af6c22a0b8002a4a9a8 wpt-pr: 13878

Bug 1499818 [wpt PR 13578] - Setup logging earlier in the wpt run startup., a=testonly 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

Bug 1506083 [wpt PR 14000] - Update interfaces/selection-api.idl, a=testonly Automatic update from web-platform-testsUpdate interfaces/selection-api.idl (#14000) Source: https://github.com/tidoust/reffy-reports/blob/83bbd56/whatwg/idl/selection-api.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/452744285 -- wpt-commits: 80d76f845c716a87bc872716db4a1dafca99315c wpt-pr: 14000

Bug 1506085 [wpt PR 14001] - Update interfaces/webrtc.idl, a=testonly Automatic update from web-platform-testsUpdate interfaces/webrtc.idl (#14001) Source: https://github.com/tidoust/reffy-reports/blob/83bbd56/whatwg/idl/webrtc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/452744285 -- wpt-commits: c506a34947682ca230cc526d7a57cb9a40a917f0 wpt-pr: 14001

Bug 1506046 [wpt PR 13995] - Do not send old capabilities to ChromeDriver, a=testonly 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

Bug 1504733 [wpt PR 13921] - Update wpt metadata, a=testonly wpt-pr: 13921 wpt-type: metadata

Bug 1504733 [wpt PR 13921] - Fetch: CORS and request's Content-Type header, a=testonly 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

Bug 1506022 [wpt PR 13993] - Update wpt metadata, a=testonly wpt-pr: 13993 wpt-type: metadata

Bug 1506022 [wpt PR 13993] - html: Fix a sanitization issue of type-change-state.html, a=testonly 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

Bug 1505726 [wpt PR 13980] - Update wpt metadata, a=testonly wpt-pr: 13980 wpt-type: metadata

Bug 1505726 [wpt PR 13980] - [media] Treat cross-origin redirect as TAINTED only for no-cors requests, a=testonly 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

Bug 1505596 [wpt PR 13969] - Reland "Make XR FrameData and Environment mojo associated", a=testonly 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

Bug 1505928 [wpt PR 13987] - Add aestes as a payment-request/ suggested reviewer., a=testonly Automatic update from web-platform-testsAdd aestes as a payment-request/ suggested reviewer. (#13987) -- wpt-commits: cc3cc477a389219fa853fa7a076acdd767e8abeb wpt-pr: 13987

Bug 1505901 [wpt PR 13986] - Update requests to 2.20.1, a=testonly Automatic update from web-platform-testsUpdate requests to 2.20.1 (#13986) -- wpt-commits: 6e6b8376c25d39c7041570e65ed9a71918a89902 wpt-pr: 13986

Bug 1505232 [wpt PR 13958] - The computed value of float with absolute positioning when there is no box should be "none", a=testonly 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

Bug 1505708 [wpt PR 13979] - [filter-effects] Add chrishtr as reviewer, a=testonly Automatic update from web-platform-tests[filter-effects] Add chrishtr as reviewer -- Merge pull request #13979 from ewilligers/filter-effects-reviewers [filter-effects] Add chrishtr as reviewer -- wpt-commits: 1ea85775c50479fb733c1a271850a47498efce14, b759b821c3f77719cadc53a58f00239b321b9b2d wpt-pr: 13979