b13df89f07865c6d9f092ed68c055d9534f6d5f1: Bug 1676537 - Do not define FILE_BASIC_INFORMATION in MinGW build. r=mhowell
Toshihito Kikuchi <tkikuchi@mozilla.com> - Wed, 11 Nov 2020 15:27:19 +0000 - rev 556813
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676537 - Do not define FILE_BASIC_INFORMATION in MinGW build. r=mhowell Differential Revision: https://phabricator.services.mozilla.com/D96718
3a4a0d02e908004257642f91c042e6359ac5673c: Bug 1676606 - [wpt-sync] Update web-platform-tests to 005f9228f0f92eb1558b8d5b2193bc7a93d5ec80, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 11 Nov 2020 10:30:12 +0000 - rev 556812
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676606 - [wpt-sync] Update web-platform-tests to 005f9228f0f92eb1558b8d5b2193bc7a93d5ec80, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 005f9228f0f92eb1558b8d5b2193bc7a93d5ec80 wpt-type: landing
815096179128907ef1d1724505b22046fa84c83b: Bug 1676566 [wpt PR 26460] - Add typedef ReadableStreamReader to readable_stream.idl, a=testonly
Nidhi Jaju <nidhijaju@google.com> - Wed, 11 Nov 2020 10:29:03 +0000 - rev 556811
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676566 [wpt PR 26460] - Add typedef ReadableStreamReader to readable_stream.idl, a=testonly Automatic update from web-platform-tests Add typedef ReadableStreamReader to readable_stream.idl In this CL, the typedef for ReadableStreamReader is added to the Readable Stream WebIDL file based on the Streams API Standard[1]. In order to avoid confusion, the ReadableStreamReader class is also renamed to ReadableStreamGenericReader. This also makes more sense as the base class for the Default and BYOB Readers. Furthermore, the return value of getReader() is also changed to use the ReadableStreamReader typedef. Due to how the bindings code works, this meant that the return type of getReader in the C++ implementation also had to be changed to void and pass the ReadableStreamReader as a parameter, which is set as the returned reader. Lastly, a new function called GetDefaultReaderForTesting() is added to support calls to getReader() and read() in the various test files without having to change the return type everywhere. [1] https://streams.spec.whatwg.org/#typedefdef-readablestreamreader Bug: 1093862 Change-Id: Icbb34470f52ddcef53e9b1fa34f3dd8f27c48198 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2524628 Commit-Queue: Nidhi Jaju <nidhijaju@google.com> Reviewed-by: Adam Rice <ricea@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#826119} -- wpt-commits: 005f9228f0f92eb1558b8d5b2193bc7a93d5ec80 wpt-pr: 26460
02a3ebde1dc7243c805bd43453dcc1d3cbab94c4: Bug 1676491 [wpt PR 26474] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 11 Nov 2020 03:17:05 +0000 - rev 556810
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676491 [wpt PR 26474] - Update wpt metadata, a=testonly wpt-pr: 26474 wpt-type: metadata
27a76751e153c98cd3cc45decbdf86f2efd2d01c: Bug 1676491 [wpt PR 26474] - Reland: Remove scroll offset rounding in position:sticky, a=testonly
Xida Chen <xidachen@chromium.org> - Wed, 11 Nov 2020 10:28:57 +0000 - rev 556809
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676491 [wpt PR 26474] - Reland: Remove scroll offset rounding in position:sticky, a=testonly Automatic update from web-platform-tests Reland: Remove scroll offset rounding in position:sticky This is a reland of this CL: https://chromium-review.googlesource.com/c/chromium/src/+/1944633 The problem of the above CL was that it incorrectly handles sticky position offset in non-ltr containers. This CL added a virtual test case for FractionalScrollOffsets flag to have more test coverages. Bug: 1010961 Change-Id: Ic51a1e812372ee97f4d5bc8a503d3be5bd282b42 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528572 Commit-Queue: Xida Chen <xidachen@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#826080} -- wpt-commits: 45b8d335da796adeab382ed5d428580e67c0cf76 wpt-pr: 26474
ed0612eb5b0bbfad52f09b356e6926a197297de2: Bug 1676495 [wpt PR 26475] - Improve will-change:transform raster scale adjustment, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Wed, 11 Nov 2020 10:28:37 +0000 - rev 556808
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676495 [wpt PR 26475] - Improve will-change:transform raster scale adjustment, a=testonly Automatic update from web-platform-tests Improve will-change:transform raster scale adjustment This fixes the issue of too big scale for will-change:transform layers by - Partly reverting crrev.com/c/2447650 to apply the change on tiny scales only. When the ideal scale is not tiny, use the original policy to clamp minimum scale to the native scale. - Increasing kMinScaleRatioForWillChangeTransform from 0.1 to 0.25 to reduce memory and number of tiles when the scale is bigger than ideal, from 100x to 16x in worst cases. Bug: 1146393 Change-Id: Ida5720f5126648c2fad0b9921781714fa006d346 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527733 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#825998} -- wpt-commits: 4cf34e3fc5d4d673dee780015ebf194db71fd500 wpt-pr: 26475
547165e407f2d403083aa11eb4d236c11ed7d9a6: Bug 1676529 [wpt PR 26467] - [LayoutNG] Find sibling spanners using the child iterator., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Wed, 11 Nov 2020 10:28:34 +0000 - rev 556807
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676529 [wpt PR 26467] - [LayoutNG] Find sibling spanners using the child iterator., a=testonly Automatic update from web-platform-tests [LayoutNG] Find sibling spanners using the child iterator. We need to update the child iterator with where we ended up, so that the check (after the outer loop) for whether we're at the end or not works as intended, so that we SetHasSeenAllChildren() if we're at the end, lest we start from the very beginning of the multicol container when resuming layout after the spanners, which would result in an "infinite" loop (well, until we run out of memory, anyway). Bug: 1052834 Change-Id: I6650e9dc2c209ef6097b067344c9cff019ee4071 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527139 Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#825983} -- wpt-commits: f9a1b19950dab7ad4d265c4c3258ca8a78b1298d wpt-pr: 26467
51685105b80e26b3c6a2766b6ab267add12f6f80: Bug 1676496 [wpt PR 26476] - Update urllib3 to 1.26.0, a=testonly
pyup-bot <github-bot@pyup.io> - Wed, 11 Nov 2020 10:28:30 +0000 - rev 556806
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676496 [wpt PR 26476] - Update urllib3 to 1.26.0, a=testonly Automatic update from web-platform-tests Update urllib3 from 1.25.11 to 1.26.0 -- wpt-commits: 5be8767f32ceb56b34970c26e4157968b9864ae8 wpt-pr: 26476
de9c45ef184937619a353645623a92631f495ad2: Bug 1675864 [wpt PR 26436] - Simulate user inputs in activation-thru-contextmenu-event.html, a=testonly
Lan Wei <lanwei@chromium.org> - Wed, 11 Nov 2020 10:28:27 +0000 - rev 556805
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1675864 [wpt PR 26436] - Simulate user inputs in activation-thru-contextmenu-event.html, a=testonly Automatic update from web-platform-tests Simulate user inputs in activation-thru-contextmenu-event.html Use testdriver Action API to simulate mouse actions in html/user-activation/activation-thru-contextmenu-event.html. Bug: 1145677 Change-Id: I8c287cd45d87e809cfa4b5967df38ed0b58d0d37 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520453 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#825963} -- wpt-commits: b3548be6cddbd39f3efb2a62c53ddf7cca2ec620 wpt-pr: 26436
bb6e53504a46c4ed150cf5ad9485ba6b86b68507: Bug 1676431 [wpt PR 26471] - Don't clear SMIL animated value if none has been set, a=testonly
Fredrik Söderqvist <fs@opera.com> - Wed, 11 Nov 2020 10:28:24 +0000 - rev 556804
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676431 [wpt PR 26471] - Don't clear SMIL animated value if none has been set, a=testonly Automatic update from web-platform-tests Don't clear SMIL animated value if none has been set Some attributes have stricter requirements about when they can be set or cleared ('class' in particular since it requires unique ElementData). Revert to the previous behavior of only clearing the animated value if we've previously set one. Bug: 1147164, 1017723 Change-Id: I43fdfa915b6bedeb7974a7f8708f4abef141c79a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2529352 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#825924} -- wpt-commits: d826a2c9705fa43209bde13d62c5eab7473c12e7 wpt-pr: 26471
6c64552394d96c8e311b517d10b193ff01ac1f89: Bug 1676131 [wpt PR 26446] - [docs] Add note that not all tests can be run in-browser, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 11 Nov 2020 10:28:19 +0000 - rev 556803
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676131 [wpt PR 26446] - [docs] Add note that not all tests can be run in-browser, a=testonly Automatic update from web-platform-tests [docs] Add note that not all tests can be run in-browser (#26446) -- wpt-commits: e540a3a66fcc3e9fe87d8db1b124f9db0e0a48b0 wpt-pr: 26446
0fa6fca741ce292f4cf552a897a7cb58d6d2b0c3: Bug 1676099 [wpt PR 26444] - Disable position:sticky in FIELDSETs, a=testonly
Kent Tamura <tkent@chromium.org> - Wed, 11 Nov 2020 10:28:16 +0000 - rev 556802
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676099 [wpt PR 26444] - Disable position:sticky in FIELDSETs, a=testonly Automatic update from web-platform-tests Disable position:sticky in FIELDSETs Currently it seems to result in invalid sticky state. Bug: 1128479, 1146925 Change-Id: I62f7b5519e2851d6d804be5937a8bded0a7985f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2525468 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#825786} -- wpt-commits: 174f8d09bd00f44a6a48c843ea9ef2950fb2cf8a wpt-pr: 26444
bbfec609e570feb8ca1dba5478e58cb19ce7a4a5: Bug 1676391 [wpt PR 26450] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Nov 2020 18:19:18 +0000 - rev 556801
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676391 [wpt PR 26450] - Update wpt metadata, a=testonly wpt-pr: 26450 wpt-type: metadata
ca3bd343ba3fd611dbfcf2268793bf833a0d2ec9: Bug 1676391 [wpt PR 26450] - Add file missing file to connection-pool tests , a=testonly
Matt Menke <mmenke@google.com> - Wed, 11 Nov 2020 10:28:08 +0000 - rev 556800
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676391 [wpt PR 26450] - Add file missing file to connection-pool tests , a=testonly Automatic update from web-platform-tests . (#26450) Co-authored-by: Matt Menke <mmenke@chromium.org> -- wpt-commits: a45897e1d964f50e013abe8b542ce4d641bb4cc7 wpt-pr: 26450
61db56db7462299236e0962ce34dcb7862e823ab: Bug 1676463 [wpt PR 26466] - Pass an absolute path in to mozrunner for the xrePath, a=testonly
jgraham <james@hoppipolla.co.uk> - Wed, 11 Nov 2020 10:28:03 +0000 - rev 556799
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676463 [wpt PR 26466] - Pass an absolute path in to mozrunner for the xrePath, a=testonly Automatic update from web-platform-tests Pass an absolute path in to mozrunner for the xrePath (#26466) Otherwise mozrunner complains -- wpt-commits: 829fedd90a0d8b79acb9eabc2c24be7b5a1113dd wpt-pr: 26466
9655d9a0b7a189f17a4fc17615b991230c21362b: Bug 1676461 [wpt PR 26464] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Nov 2020 20:15:58 +0000 - rev 556798
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676461 [wpt PR 26464] - Update wpt metadata, a=testonly wpt-pr: 26464 wpt-type: metadata
1d008c0339df3e37ad547a69c61786257181e857: Bug 1676461 [wpt PR 26464] - Clamp frameset cols/rows values safely to integers., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Wed, 11 Nov 2020 10:27:54 +0000 - rev 556797
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676461 [wpt PR 26464] - Clamp frameset cols/rows values safely to integers., a=testonly Automatic update from web-platform-tests Clamp frameset cols/rows values safely to integers. Avoid undefined behavior, such as negative values, when casting from double to int. Bug: 1116832 Change-Id: I49d4d5c6e73a9441d20c8a502c3d9d8cff71b7d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528529 Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#825754} -- wpt-commits: c147a9c062a825dbac915d3b7639ab76d9630434 wpt-pr: 26464
0720f62f9a450d67ed8a867703d2933bf4e96d27: Bug 1676387 [wpt PR 26455] - Fix |LayoutNGBlockFlowMixin::InlineBlockBaseline|, a=testonly
Koji Ishii <kojii@chromium.org> - Wed, 11 Nov 2020 10:27:49 +0000 - rev 556796
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1676387 [wpt PR 26455] - Fix |LayoutNGBlockFlowMixin::InlineBlockBaseline|, a=testonly Automatic update from web-platform-tests Fix |LayoutNGBlockFlowMixin::InlineBlockBaseline| r824961 crrev.com/c/2515933 copied the code from |LayoutBlock| but the code in |LayoutBlockFlow| that prevents it from running when |ChildrenInline| was not copied. This patch adds the check. Note, the test creates |LayoutNGCustom| in legacy, and adds a |LayoutTextFragment| as a child of the |LayoutNGCustom|. Not to blockify the child is likely an issue in |LayoutNGCustom|, but this case could probably be reproduced by inline custom layout or other inline objects that forces NG. Bug: 1146789 Change-Id: I7ffacc2465ad205d13702dfda03433cc50c423f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2526702 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#825714} -- wpt-commits: 8f4fe33ea111e7f58c0365da6a62820b19cdd990 wpt-pr: 26455
ae756f0230ee38f736fc5b416eec645e5e522743: Bug 1669213 [wpt PR 25979] - Get the gitignore cache working, consistently use fast JSON modules, a=testonly
Sam Sneddon <gsnedders@apple.com> - Wed, 11 Nov 2020 10:27:46 +0000 - rev 556795
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1669213 [wpt PR 25979] - Get the gitignore cache working, consistently use fast JSON modules, a=testonly Automatic update from web-platform-tests Get the gitignore cache working, consistently use fast JSON modules (#25979) * Avoid relying on curdir being "" and not "." At the moment it's always ".", but it's a non-obvious performance trap if we ever do change the behaviour here * Get the gitignore cache actually working * Use quicker JSON modules as much as possible * Rename the gitignore.json cache file Problematically, older versions of the manifest on Python 3 break after this PR when the gitignore.json cache file exists. -- wpt-commits: 5a5052e5abc6087f15216095d8b2857a87c8475f wpt-pr: 25979
f3a2af43d052255be409dc5d43d40da402d80511: Bug 1668024 [wpt PR 25841] - Remove 'signed' from send-srr and srr-token-redemption., a=testonly
Steven Valdez <svaldez@chromium.org> - Wed, 11 Nov 2020 10:27:42 +0000 - rev 556794
Push 37941 by ncsoregi@mozilla.com at Thu, 12 Nov 2020 03:32:32 +0000
Bug 1668024 [wpt PR 25841] - Remove 'signed' from send-srr and srr-token-redemption., a=testonly Automatic update from web-platform-tests Remove 'signed' from send-srr and srr-token-redemption. As part of the generalization of the Trust Token redemption record, the protocol no longer specifies these as needing to be 'signed', so the API types are updated to match, from send-srr to send-redemption-record and srr-token-redemption to token-redemption. Design: https://docs.google.com/document/d/1-4n1RLaJs8ANw34TsS6BVt7ARa7lK70F6aHFG2CL3Rc/edit#heading=h.6a92f2gfl9le Bug: 1133310 Change-Id: Id6d668d10f59f3f0eac6a8f423e7c9a59134f2de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437697 Commit-Queue: Steven Valdez <svaldez@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: David Bertoni <dbertoni@chromium.org> Reviewed-by: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#825609} -- wpt-commits: b3a29a9c6b2c3622b4ce71786bb83ecd5a7d5b42 wpt-pr: 25841
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip