d1583c5916b95e5886c7e170908a68064ad20422: Bug 1631939 [wpt PR 23152] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 25 Apr 2020 02:02:36 +0000 - rev 527258
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1631939 [wpt PR 23152] - Update wpt metadata, a=testonly wpt-pr: 23152 wpt-type: metadata
7b9acbee64f66fff208f2490ff5ab2321c6d73b2: Bug 1631939 [wpt PR 23152] - [EventTiming] Implement durationThreshold, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Tue, 28 Apr 2020 11:44:00 +0000 - rev 527257
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1631939 [wpt PR 23152] - [EventTiming] Implement durationThreshold, a=testonly Automatic update from web-platform-tests [EventTiming] Implement durationThreshold This CL implements a durationThreshold member of PerformanceObserverInit which enables setting a threshold for the event timing entries received by a PerformanceObserver. The entries are still buffered per the default duration threshold of 104 for now. Tests are added for various threshold values. PR: https://github.com/WICG/event-timing/pull/82 Bug: 543598 Change-Id: Id3407ddbcd1713fc33036518bbf88696add423cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159611 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#762168} -- wpt-commits: c7f5f1561f751232d7577d21808e45af289a2d46 wpt-pr: 23152
614b8a80a6a0461b74ff28d4a2a3ad81b1c6e7e5: Bug 1632883 [wpt PR 23233] - Be responsive to reference box changes for transformed containers, a=testonly
Fredrik Söderqvist <fs@opera.com> - Tue, 28 Apr 2020 11:43:55 +0000 - rev 527256
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632883 [wpt PR 23233] - Be responsive to reference box changes for transformed containers, a=testonly Automatic update from web-platform-tests Be responsive to reference box changes for transformed containers This adapts the technique used elsewhere to work with LayoutSVGContainers (specifically LayoutSVGTransformableContainer). Bug: 697052, 1074080 Change-Id: I5dc1ca440aaa2d76eb49ae54fb0c4422f166c4f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165107 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#762562} -- wpt-commits: 15f0671b0ebffbe0d7fd64fdbdb4f2e69fb0eb3e wpt-pr: 23233
4ba949f441f99033fe9d9afee9c2ed6de744403f: Bug 1632885 [wpt PR 23234] - Account for root element paint offset when painting backgrounds, a=testonly
Philip Rogers <pdr@chromium.org> - Tue, 28 Apr 2020 11:43:50 +0000 - rev 527255
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632885 [wpt PR 23234] - Account for root element paint offset when painting backgrounds, a=testonly Automatic update from web-platform-tests Account for root element paint offset when painting backgrounds The root background is painted from the coordinate space of the root element, but expands to fill the viewport. The difference between these spaces needs to be used as an offset when painting the background. For the non-transform case, this patch removes the paint offset adjustment made to the entire paint rect in ViewPainter, and only applies the paint offset for positioning the background in BackgroundImageGeometry::ComputePositioningArea. This way, painting starts from the origin, without paint offset. For the transform case, paint properties will apply the paint offset, and the entire paint rect needs to be adjusted to remove the paint offset. This patch specifies the transform state of the view and root element, and uses GeometryMapper to map the background paint rect into the coordinate space of the root element. A TODO has been added to more clearly specify the non-transform and transform cases. Bug: 1071957 Change-Id: Iedc1834ef9c400340b668b3eec73a0f3f4506194 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161350 Auto-Submit: Philip Rogers <pdr@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#762543} -- wpt-commits: f8bd87deb2c2a0ea974adb6c64ef013a60188193 wpt-pr: 23234
f2fe2ea32a80b1a42ad48d6d0c90b1981b64d213: Bug 1632882 [wpt PR 23232] - [ua-ch] s/uaList/brands/, a=testonly
Yoav Weiss <yoavweiss@chromium.org> - Tue, 28 Apr 2020 11:43:45 +0000 - rev 527254
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632882 [wpt PR 23232] - [ua-ch] s/uaList/brands/, a=testonly Automatic update from web-platform-tests [ua-ch] s/uaList/brands/ This aligns the UA-CH implementation with [1] [1] https://github.com/WICG/ua-client-hints/pull/99 Change-Id: I903450f3103c7068aa7548b69b986593d13d8904 Bug: 1074338 Change-Id: I903450f3103c7068aa7548b69b986593d13d8904 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2164526 Reviewed-by: Aaron Tagliaboschi <aarontag@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#762448} -- wpt-commits: c0129ead75677b772594d7c41b9da836ecaf5019 wpt-pr: 23232
d58755c3fd90dafacf9596d80508e708ab876394: Bug 1632703 [wpt PR 23220] - Create LayoutShiftAttribution objects in LayoutShiftTracker., a=testonly
Steve Kobes <skobes@chromium.org> - Tue, 28 Apr 2020 11:43:40 +0000 - rev 527253
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632703 [wpt PR 23220] - Create LayoutShiftAttribution objects in LayoutShiftTracker., a=testonly Automatic update from web-platform-tests Create LayoutShiftAttribution objects in LayoutShiftTracker. Also mark the REF "experimental", so that it is tested, and add a test. Bug: 1053510 Change-Id: I8bac9c8002d20991599a1bf396f28dd9101b0f63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157988 Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Commit-Queue: Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#762442} -- wpt-commits: a7b88cb7b8ba75a5399aee54540f03bb88924672 wpt-pr: 23220
31e479ea76050bebac5cec49cdcda084a0f3b621: Bug 1632608 [wpt PR 23211] - WPT Chromium logger bug fixes to integrate with results viewer., a=testonly
Luke Zielinski <lpz@chromium.org> - Tue, 28 Apr 2020 11:43:35 +0000 - rev 527252
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632608 [wpt PR 23211] - WPT Chromium logger bug fixes to integrate with results viewer., a=testonly Automatic update from web-platform-tests WPT Chromium logger bug fixes to integrate with results viewer. Three main issues fixed here: 1. Removing a trailing whitespace in the "expected" field. This is caused by "known_intermittent" always being present in the test_end data dict, but simply being empty when no intermittent statuses exist. 2. Making sure the start timestamp is always in seconds - the wpt test framework provides it in microseconds, but we can fallback to "now" which returns seconds. 3. All artifacts are expected to be lists. Bug: 1070265 Change-Id: I3dc98f8e37d847727c3165ab51c293f529d3c5eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163065 Commit-Queue: Robert Ma <robertma@chromium.org> Auto-Submit: Luke Z <lpz@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#762415} -- wpt-commits: 01aed092cae7983b2d4ecf29097e33ce4e9af5b9 wpt-pr: 23211
9a0cd8abc9b59f98033c72b68c831e4feb3ef966: Bug 1632905 [wpt PR 23235] - [client hints] Add WPTs for subresource redirects, a=testonly
Aaron Tagliaboschi <aarontag@chromium.org> - Tue, 28 Apr 2020 11:43:25 +0000 - rev 527251
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632905 [wpt PR 23235] - [client hints] Add WPTs for subresource redirects, a=testonly Automatic update from web-platform-tests [client hints] Add WPTs for subresource redirects Making sure subresource *don't* register client hint preferences on redirects. Bug: 1042828 Change-Id: I050e81e9473ce7c771763d9b18fc2e1843ab5546 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154849 Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#762401} -- wpt-commits: 39e9c51041a1be64b61281ddc2381ffe33d05b84 wpt-pr: 23235
6b001eb70b3328cad408e3550e2f79f185102c51: Bug 1632819 [wpt PR 23228] - Update interfaces/webrtc-stats.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 28 Apr 2020 11:43:20 +0000 - rev 527250
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632819 [wpt PR 23228] - Update interfaces/webrtc-stats.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webrtc-stats.idl (#23228) Source: https://github.com/tidoust/reffy-reports/blob/eeef44a/ed/idl/webrtc-stats.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/679007987 -- wpt-commits: c430c87d74939e9a10fbf00782fa49669ec0bd5b wpt-pr: 23228
8be3ce5bbf792efdda1ffd1b2efd23e2c5bc8343: Bug 1632816 [wpt PR 23227] - Mark clipboard-apis/async-idlharness.https.html as timeout=long, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:43:08 +0000 - rev 527249
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632816 [wpt PR 23227] - Mark clipboard-apis/async-idlharness.https.html as timeout=long, a=testonly Automatic update from web-platform-tests Mark clipboard-apis/async-idlharness.https.html as timeout=long This is symptomatic of crbug.com/1047818, but to stop the pain for sheriffs lets mark it timeout=long for now. Bug: 1073055 Change-Id: I1e17f6a0fe2dc66f4c842b80361057cb19a3edc6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2163955 Reviewed-by: Luke Z <lpz@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#762348} -- wpt-commits: a6396b8566a7a85fa2ce33abfc480cc7e48574aa wpt-pr: 23227
6483fc7ffd411592d9aca3727c80f9c248a4e357: Bug 1621081 [wpt PR 22145] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 15:39:26 +0000 - rev 527248
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1621081 [wpt PR 22145] - Update wpt metadata, a=testonly wpt-pr: 22145 wpt-type: metadata
38fcdb8fde8a25b794b4d1048085802beb191546: Bug 1621081 [wpt PR 22145] - Use assert_implements in test the-input-element/type-change-state.html, a=testonly
Carlos Alberto Lopez Perez <clopez@igalia.com> - Tue, 28 Apr 2020 11:43:00 +0000 - rev 527247
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1621081 [wpt PR 22145] - Use assert_implements in test the-input-element/type-change-state.html, a=testonly Automatic update from web-platform-tests Use assert_implements in test the-input-element/type-change-state.html (#22145) * Use assert_implements to check if the browser supports both input element types before trying to change the state from one to other. * For example, WebKitGTK and Safari doesn't support several of the input types tested here (like those related to dates). The output of the test its clearer if the precondition its checked before. -- wpt-commits: af8fb743e877884ae9f6cec97a60da6e22d06740 wpt-pr: 22145
00be66227a0c18fd63d230b84163871ab2fb6edf: Bug 1619698 [wpt PR 22068] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 14:44:35 +0000 - rev 527246
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1619698 [wpt PR 22068] - Update wpt metadata, a=testonly wpt-pr: 22068 wpt-type: metadata
28d1dd0a877e8d959b5b75429e19c44d36f76729: Bug 1619698 [wpt PR 22068] - [client hints] Fix handling of redirects in navigation, a=testonly
Maks Orlovich <morlovich@chromium.org> - Tue, 28 Apr 2020 11:42:52 +0000 - rev 527245
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1619698 [wpt PR 22068] - [client hints] Fix handling of redirects in navigation, a=testonly Automatic update from web-platform-tests [client hints] Fix handling of redirects in navigation In particular, the browser needs to handle accept-ch there since the renderer doesn't see the intermediate steps until after everything is fetched, and new client hints may be requested in the middle of the chain. This is done by having the network service parse the header and store in ParseHeaders, then using that in the browser This is also likely the first step towards moving more of handling of accept-ch to browser (which will simplify some things and fix some bugs). Bug: 1050726 Change-Id: Ie02d7492c02b75034b36af30e489ebbb430d6a1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2085114 Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#762329} -- wpt-commits: 39411b7ef888f9bd67e430970042f757bac0bed0 wpt-pr: 22068
ed06ca73fddfdc5073257aef59b31240f0c4e3f9: Bug 1631900 [wpt PR 23150] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 13:15:46 +0000 - rev 527244
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1631900 [wpt PR 23150] - Update wpt metadata, a=testonly wpt-pr: 23150 wpt-type: metadata
d5aefccd6b07332f0b13a0f76d0f4aca200134f8: Bug 1631900 [wpt PR 23150] - Update interfaces/html.idl, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:42:42 +0000 - rev 527243
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1631900 [wpt PR 23150] - Update interfaces/html.idl, a=testonly Automatic update from web-platform-tests Update interfaces/html.idl (#23150) Includes necessary idlharness.js updates (handling XYZ --> LegacyXYZ renames) for https://github.com/web-platform-tests/wpt/issues/23148 Closes https://github.com/web-platform-tests/wpt/pull/23124 -- wpt-commits: 513fe4fe493fd1215987460781345e9fc4cc7b0d wpt-pr: 23150
4ef12cfc7a604c3617ff2fb7e441f1c114435a63: Bug 1628916 [wpt PR 22833] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 10:07:01 +0000 - rev 527242
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1628916 [wpt PR 22833] - Update wpt metadata, a=testonly wpt-pr: 22833 wpt-type: metadata
10e8bc75d539a5f6c8b4d4ff91c47c29cdad8ec8: Bug 1628916 [wpt PR 22833] - WASM JS API: Test cross-realm default [[Prototype]] value, a=testonly
Alexey Shvayka <shvaikalesh@gmail.com> - Tue, 28 Apr 2020 11:42:34 +0000 - rev 527241
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1628916 [wpt PR 22833] - WASM JS API: Test cross-realm default [[Prototype]] value, a=testonly Automatic update from web-platform-tests WASM JS API: Test cross-realm default [[Prototype]] value -- Test all primitives, add evil tests, don't reuse NewTarget -- Use `format_value` harness -- wpt-commits: ea3647bed43a67a037dab8d034c788b000deb630, d64c23fbaa6f2e2570525c21504adb7c352cbe6c, 028bd865075804de1e5f1d5bfbd01b5993ce5b45 wpt-pr: 22833
feacdb5d1e3f0c891141f55e58518849f21e1fd9: Bug 1632382 [wpt PR 23194] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 24 Apr 2020 07:54:03 +0000 - rev 527240
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632382 [wpt PR 23194] - Update wpt metadata, a=testonly wpt-pr: 23194 wpt-type: metadata
5f6680be8c1fb6229fc67131a0a44b9273d246ea: Bug 1632382 [wpt PR 23194] - [css-flexbox] Implement gap/gutters, a=testonly
David Grogan <dgrogan@chromium.org> - Tue, 28 Apr 2020 11:42:26 +0000 - rev 527239
Push 37366 by cbrindusan@mozilla.com at Fri, 01 May 2020 09:42:47 +0000
Bug 1632382 [wpt PR 23194] - [css-flexbox] Implement gap/gutters, a=testonly Automatic update from web-platform-tests [css-flexbox] Implement gap/gutters This only works when you enable "Enable experimental web platform features" in about:flags. This patch doesn't implement a weird case that firefox supports: resolving a percent column-gap when the flexbox's height is indefinite. This patch resolves it to 0. We may wait until that is fixed before exposing this to the web without the about:flag. The relevant test is http://wpt.live/css/vendor-imports/mozilla/mozilla-central-reftests/flexbox/flexbox-column-row-gap-004.html The spec issue is https://github.com/w3c/csswg-drafts/issues/4664. This patch does not include the few engine-specific bits in legacy, so gap only works in FlexNG. Change-Id: I691889cf4b9346e94c83ef655dc9fd6eebca640d Bug: 762679, 845235 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2162149 Commit-Queue: David Grogan <dgrogan@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#762264} -- wpt-commits: 344e2aa99d6555e12d0003fb6cbf7abf0c5fd64a wpt-pr: 23194
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip