5acad8eeb0b40a9c5dc994fcdc0aa4ee3120c090: Bug 1604968 [wpt PR 20857] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 20 Dec 2019 20:18:13 +0000 - rev 574267
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1604968 [wpt PR 20857] - Update wpt metadata, a=testonly wpt-pr: 20857 wpt-type: metadata
cbb3d940c61a17fd52b843f81b65184d99a60c41: Bug 1604968 [wpt PR 20857] - Enable file uploads in web_tests via testdriver-vendor.js., a=testonly
Marijn Kruisselbrink <mek@chromium.org> - Thu, 02 Jan 2020 10:51:06 +0000 - rev 574266
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1604968 [wpt PR 20857] - Enable file uploads in web_tests via testdriver-vendor.js., a=testonly Automatic update from web-platform-tests Enable file uploads in web_tests via testdriver-vendor.js. testdriver supports file uploads via send_keys to the input element, on the other hand eventSender supports file uploads via drag&drop to the input element. So this CL implements test_driver_internal.send_keys by using the drag&drop functionality if the target element is an <input type=file>. Also fixes a bug in file_upload.sub.html where backslashes in the file path weren't being escaped, resulting in the test not working on windows. Change-Id: I9a446f8dac3ae7817bb03ba9592d2537223b0f33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974849 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#726873} -- wpt-commits: c8158bdeea965ceecd5a95d507e75e863fdc6d0e wpt-pr: 20857
aba0683e98192cb6806fe8249928ea035f75d14e: Bug 1599568 [wpt PR 20459] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 20 Dec 2019 18:45:35 +0000 - rev 574265
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1599568 [wpt PR 20459] - Update wpt metadata, a=testonly wpt-pr: 20459 wpt-type: metadata
9e281a19eb3d8a79a92cb1189d7f118cb4fff4fa: Bug 1599568 [wpt PR 20459] - Change how wptrunner computes reftests, a=testonly
Sam Sneddon <me@gsnedders.com> - Thu, 02 Jan 2020 10:50:58 +0000 - rev 574264
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1599568 [wpt PR 20459] - Change how wptrunner computes reftests, a=testonly Automatic update from web-platform-tests Change how wptrunner computes reftests (#20459) This preserves the current data structures within wptrunner as it passes them onwards to Marionette currently in the Firefox case, and as such changing them involves changes within Firefox too. Those changes within Firefox are ones we should make, and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1598340, before changing how reftests are represented within wptrunner. -- wpt-commits: e9fe7bf0c8d0d48f4fc36d6631c1d05af071792c wpt-pr: 20459
ed7b50d58548b280448cbd569ca28a5890f90c50: Bug 1604878 [wpt PR 20847] - Add a way to signal AR support through FakeXRDeviceInit, a=testonly
Piotr Bialecki <bialpio@chromium.org> - Thu, 02 Jan 2020 10:50:53 +0000 - rev 574263
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1604878 [wpt PR 20847] - Add a way to signal AR support through FakeXRDeviceInit, a=testonly Automatic update from web-platform-tests Add a way to signal AR support through FakeXRDeviceInit Aligns our MockRuntime implementation to changes introduced by: https://github.com/immersive-web/webxr-test-api/pull/45 Change-Id: Icd33b566118501457c338a1d7882d260bf3f48e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974310 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Auto-Submit: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#726856} -- wpt-commits: cfa8792159ff63e208d4133ce692d2980bb41f90 wpt-pr: 20847
8438a4a1870add21cb5cecac6550a2b8373a111f: Bug 1605149 [wpt PR 20864] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 20 Dec 2019 19:41:40 +0000 - rev 574262
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1605149 [wpt PR 20864] - Update wpt metadata, a=testonly wpt-pr: 20864 wpt-type: metadata
970852e7787120e2e054fd941ed535867e69d720: Bug 1605149 [wpt PR 20864] - [css-pseudo] Properly set 'display: inline-block' to outside ::marker, a=testonly
Oriol Brufau <obrufau@igalia.com> - Thu, 02 Jan 2020 10:50:43 +0000 - rev 574261
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1605149 [wpt PR 20864] - [css-pseudo] Properly set 'display: inline-block' to outside ::marker, a=testonly Automatic update from web-platform-tests [css-pseudo] Properly set 'display: inline-block' to outside ::marker Before this patch, outside markers were assigned 'display: inline-block' but this happened in two different places: in LayoutNGListItem for markers with 'content: normal', and in StyleAdjuster for content ones. However, this meant that 'getComputedStyle(el, "::marker").display' would be 'inline' in the former case and 'inline-block' in the latter. This patch fixes that issue by ensuring that StyleAdjuster runs for all markers, assigning 'display: inline-block' to outside ones even when 'content: normal'. This has a noticeable effect even if the CSSMarkerPseudoElement flag is disabled: text decorations are no longer propagated to outside markers. This is actually expected, since decorations shouldn't be propagated to inline-block descendants. They were being propagated for markers with 'content: normal' because the code that stops the propagation either wasn't running for unstyled markers, or for styled normal markers it was running before 'display: inline-block' was assigned. This change won't be a compat problem since none of Chromium legacy, Firefox and Edge propagate text decorations to outside markers by default. Doing it seemed a LayoutNG bug. Spec: https://drafts.csswg.org/css-pseudo-4/#marker-pseudo Spec: https://drafts.csswg.org/css-lists/#list-style-position Spec: https://drafts.csswg.org/css-text-decor-4/#line-decoration BUG=457718 TEST=external/wpt/css/css-pseudo/marker-content-016.html TEST=external/wpt/css/css-pseudo/marker-display-computed.html The marker-content-016 test fails in legacy since the 'content' property is not supported yet in ::marker Change-Id: Ia1396a4f6c5d9825dba5a6265c32096a7066fbed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975887 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#726783} -- wpt-commits: 2cb652e543d379bafcb3d0d26e2de28836f22df4 wpt-pr: 20864
338a7fd63bc46d92f818d43fae72ca474258d5f3: Bug 1604628 [wpt PR 20819] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 20 Dec 2019 19:42:55 +0000 - rev 574260
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1604628 [wpt PR 20819] - Update wpt metadata, a=testonly wpt-pr: 20819 wpt-type: metadata
ce9050847bad735fd97c6fa45f278d47fa158f20: Bug 1604628 [wpt PR 20819] - [EventTiming] Fix crossiframe test, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Thu, 02 Jan 2020 10:50:35 +0000 - rev 574259
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1604628 [wpt PR 20819] - [EventTiming] Fix crossiframe test, a=testonly Automatic update from web-platform-tests [EventTiming] Fix crossiframe test This CL does the following fixes to crossiframe.html test: * Remove slow-image and onload, which are obsolete assumptions. Instead, rely solely on PerformanceObserver. * Use awaits where needed to make the test logic more sequential. * Use coordinates and test_driver.Actions() to target the iframe. Using the test_driver.click directly won't work for elements in iframes. * Updates the test to check reasonable values for the frame and iframe entries and check that they don't receive each other's entries. This CL also: * Removes unneeded variables from the clickAndBlockMain(). * Removes manual test, which is no longer needed. Bug: 831729 Change-Id: Iff50035a216b21f67cd71796023af4f934573086 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972249 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#726422} -- wpt-commits: 80e94e6d5113f3670e0b36c0a1fd905a43ce65d5 wpt-pr: 20819
92eb9c69c3db6a48e1433f396a7dc863b434add7: Bug 1605202 [wpt PR 20872] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 20 Dec 2019 19:12:47 +0000 - rev 574258
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1605202 [wpt PR 20872] - Update wpt metadata, a=testonly wpt-pr: 20872 wpt-type: metadata
2a0d192f6af38b5fc6576a5936ff11e38a40f4f1: Bug 1605202 [wpt PR 20872] - Roll WebGPU CTS, a=testonly
Kai Ninomiya <kainino@chromium.org> - Thu, 02 Jan 2020 10:50:27 +0000 - rev 574257
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1605202 [wpt PR 20872] - Roll WebGPU CTS, a=testonly Automatic update from web-platform-tests Roll WebGPU CTS Reviewed upstream. TBR: cwallez@chromium.org Change-Id: I1bac1e7abd7f5b8e932bad6c6a591311178f239c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975999 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#726472} -- wpt-commits: f904e29d0370a621b10cb271e044264e6d882543 wpt-pr: 20872
04dd59867d611c1a73b9e50c70b4244a3c6a860d: Bug 1605375 [wpt PR 20889] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 20 Dec 2019 18:36:35 +0000 - rev 574256
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1605375 [wpt PR 20889] - Update wpt metadata, a=testonly wpt-pr: 20889 wpt-type: metadata
7a1d92e2a3a1a7eaf04084a543c99dbf8e1d7397: Bug 1605375 [wpt PR 20889] - Refactor data-feeding for ImageDocument/ImageDocumentParser, a=testonly
Fredrik Söderquist <fs@opera.com> - Thu, 02 Jan 2020 10:50:19 +0000 - rev 574255
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1605375 [wpt PR 20889] - Refactor data-feeding for ImageDocument/ImageDocumentParser, a=testonly Automatic update from web-platform-tests Refactor data-feeding for ImageDocument/ImageDocumentParser ImageDocumentParser keeps the ImageResource for ImageDocument and passes the associated ImageResourceContent to the HTMLImageElement used for the ImageDocument. This eliminates ImageDocument::CachedImageResourceDeprecated and cleans up ImageDocument<->ImageDocumentParser interaction a bit. The creation of the ImageResource now takes place in the first call to ImageDocumentParser::AppendBytes rather than indirectly via a call to ImageDocument::CachedImage. Set ImageLoader::image_complete_ in the same as for regular image-loads, and start dispatching 'load' (and 'error') events for the <img> element in the image document. This behavior matches Gecko. Bug: 958339 Change-Id: Iacdab89f6894adf70163f0d5300aefc9b2fce4e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975921 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#726803} -- wpt-commits: 25ec2153abd47ea8b7a8cba23b3f153167c0805d wpt-pr: 20889
2a33bd3d46970f58ff5680911904e8256f33fed8: Bug 1602531 [wpt PR 20682] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 19 Dec 2019 20:25:21 +0000 - rev 574254
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1602531 [wpt PR 20682] - Update wpt metadata, a=testonly wpt-pr: 20682 wpt-type: metadata
0fecc15875a40815d33bddb2c50807736bc1cd18: Bug 1602531 [wpt PR 20682] - [css-layout-api] IntrinsicSizes Implementation, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 02 Jan 2020 10:50:11 +0000 - rev 574253
Push 2247 by ffxbld-merge at Mon, 03 Feb 2020 09:19:36 +0000
Bug 1602531 [wpt PR 20682] - [css-layout-api] IntrinsicSizes Implementation, a=testonly Automatic update from web-platform-tests [css-layout-api] IntrinsicSizes Implementation This change adds support for the CSS Layout API intrinsicSizes() callback function. The implementation closely matches that of the layout() callback function. - Spec: https://drafts.css-houdini.org/css-layout-api/#intrinsicsizes - Algorithm: https://drafts.css-houdini.org/css-layout-api/#invoke-an-intrinsic-sizes-callback The implementation also involved exposure of the IntrinsicSizesResultOptions type. - Spec: https://drafts.css-houdini.org/css-layout-api/#dictdef-intrinsicsizesresultoptions Support was also added for the Child intrinsicSizes() function. - Spec: https://drafts.css-houdini.org/css-layout-api/#dom-layoutchild-intrinsicsizes - Algorithm: https://drafts.css-houdini.org/css-layout-api/#dom-layoutchild-intrinsicsizes Bug: 726125 Change-Id: Ifc6064e069b4c9c5218c9d783b7d9de6a480e7ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949536 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#725834} -- Rename some colliding references -- wpt-commits: f160db31bb6fdf94c6c914a779a1b47b9e0e4e30, 5f8d15ebdcf0495c271c81776971061be1366445 wpt-pr: 20682
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 +10000 +30000 +100000 tip