f334045e42065314792b474eb5519af750460d0c: Bug 1651872 [wpt PR 24549] - Update interfaces/native-file-system.idl, a=testonly
autofoolip <auto@foolip.org> - Fri, 17 Jul 2020 11:13:31 +0000 - rev 541044
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651872 [wpt PR 24549] - Update interfaces/native-file-system.idl, a=testonly Automatic update from web-platform-tests Update interfaces/native-file-system.idl (#24549) Source: https://github.com/tidoust/reffy-reports/blob/36f1e58/ed/idl/native-file-system.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/706723894 -- wpt-commits: efbfe977d5a5a4959c0bbc8d36abc26f27e24f28 wpt-pr: 24549
12ef948ccdb767c5e5ac53e8a3f596ad0bb25c03: Bug 1651201 [wpt PR 24496] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 01:56:40 +0000 - rev 541043
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651201 [wpt PR 24496] - Update wpt metadata, a=testonly wpt-pr: 24496 wpt-type: metadata
e302332c2b3dbebbfbb9811fde4e1e64ab0305ce: Bug 1651201 [wpt PR 24496] - WebXR - anchors - add WPTs for more complete coverage of the API, a=testonly
Piotr Bialecki <bialpio@chromium.org> - Fri, 17 Jul 2020 11:13:23 +0000 - rev 541042
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651201 [wpt PR 24496] - WebXR - anchors - add WPTs for more complete coverage of the API, a=testonly Automatic update from web-platform-tests WebXR - anchors - add WPTs for more complete coverage of the API Change-Id: I0a0858835a040161b352f465d68c068a8d4847bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284094 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#786984} -- wpt-commits: ce7bfaec86b1c6c926bdb0f2150e33a3a1bf1f54 wpt-pr: 24496
4f79afc7b4f6cff44808d28c06f0adef752cc374: Bug 1651805 [wpt PR 24539] - [LayoutNG] Spanner break token and fragmentation improvements., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 17 Jul 2020 11:13:18 +0000 - rev 541041
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651805 [wpt PR 24539] - [LayoutNG] Spanner break token and fragmentation improvements., a=testonly Automatic update from web-platform-tests [LayoutNG] Spanner break token and fragmentation improvements. We were creating incorrect outgoing break tokens from column content that was interrupted by two or more adjacent spanners. The outgoing break token would point to the second spanner, rather than any column content that would follow. To fix this, make sure that we don't interrupt column layout until we have looked past all adjacent spanners, to find the right place to resume column layout right away. This gets especially more fun if we're nested inside another fragmentation context, because then we may not be able to resume column content layout in the same outer fragmentation. Therefore we need to keep proper track of all the spanner break tokens. Introduce a walker to streamline processing of the multicol parts (spanners and/or column content), and thus make LayoutChildren() easier to follow. We're now also better at handling parallel flows established inside spanners. Bug: 1066617, 829028 Change-Id: I7ad3f8f19f7258e2f8a588034c0002249efdaf20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2288705 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#786940} -- wpt-commits: 0b58efec76d3f460dbb65d577e46ba4daf781427 wpt-pr: 24539
0e5aa1bbee74d74a6bbe65832b16ee10073f9442: Bug 1651803 [wpt PR 24538] - [LayoutNG] Handle spanner margins correctly across fragments., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 17 Jul 2020 11:13:13 +0000 - rev 541040
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651803 [wpt PR 24538] - [LayoutNG] Handle spanner margins correctly across fragments., a=testonly Automatic update from web-platform-tests [LayoutNG] Handle spanner margins correctly across fragments. Use the same AdjustMarginsForFragmentation() utility function as in regular block layout, so that we handle block-end margins correctly, i.e. apply them to only one fragment (which may not necessarily be the last one, if something inside the spanner establishes a parallel flow). Bug: 829028 Change-Id: I307037a23f960dc4ed4db2c126e41c59de8ae38e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2289134 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#786948} -- wpt-commits: 0dc51c3f662dcb23da4c60255abe0bd333c8e37e wpt-pr: 24538
50ffdda1ea01029c273949d266526bba1a7a2e87: Bug 1651213 [wpt PR 24498] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 00:37:07 +0000 - rev 541039
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651213 [wpt PR 24498] - Update wpt metadata, a=testonly wpt-pr: 24498 wpt-type: metadata
b44b9807dc48dff4dfd10f7dfda69ad16e988212: Bug 1651213 [wpt PR 24498] - Origin isolation: add various navigation WPTs, a=testonly
Domenic Denicola <domenic@chromium.org> - Fri, 17 Jul 2020 11:13:04 +0000 - rev 541038
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651213 [wpt PR 24498] - Origin isolation: add various navigation WPTs, a=testonly Automatic update from web-platform-tests Origin isolation: add various navigation WPTs This adds web platform tests covering various navigation scenarios for origin isolation. The intention is to cover at least all the non-popup navigation cases in isolated_origin_browsertest.cc. We also want to approach the same coverage for navigation as we have for two-iframe scenarios (i.e. the various parent-child1-child2 tests), but we avoid doubling the size of the test suite by focusing on the more important or tricky scenarios instead of just copying all of those. Bug: 1042415 Change-Id: Ifb937f183af2610f348e4fea036d96aa0504ddab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285258 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by: James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#786945} -- wpt-commits: 9d71a04aef33467e378c662d8b58ab1df6ff7719 wpt-pr: 24498
233273997afc1ad76420ee24d364321dee2ca429: Bug 1651831 [wpt PR 24542] - Add comment to border-width-011 to make it immediately obvious, a=testonly
Sam Sneddon <me@gsnedders.com> - Fri, 17 Jul 2020 11:12:59 +0000 - rev 541037
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651831 [wpt PR 24542] - Add comment to border-width-011 to make it immediately obvious, a=testonly Automatic update from web-platform-tests Add comment to border-width-011 to make it immediately obvious (#24542) -- wpt-commits: fd21e757f91e0858a1a2b3870a3c1fb3a59dbd14 wpt-pr: 24542
a3d6861bc3d89e840ad546934b439c68bb0def7d: Bug 1650806 [wpt PR 24460] - Change document policy parser to use structured header dictionary, a=testonly
Charlie Hu <chenleihu@google.com> - Fri, 17 Jul 2020 11:12:54 +0000 - rev 541036
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1650806 [wpt PR 24460] - Change document policy parser to use structured header dictionary, a=testonly Automatic update from web-platform-tests Change document policy parser to use structured header dictionary This CL is based on the spec change on https://github.com/w3c/webappsec-feature-policy/pull/388/files?short_path=1a56774. Since the parameter names are removed in this change, feature names will have to change so that they remain meaningful. This will be addressed in follow-up CLs. Change-Id: Ic87dcb5bf26e440dd5041ae31d7b248e7d85d93a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2281104 Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Commit-Queue: Charlie Hu <chenleihu@google.com> Cr-Commit-Position: refs/heads/master@{#786929} -- wpt-commits: 78d5125d6c9e0e48accc6040499db5477d5c311b wpt-pr: 24460
c951ba559d35c59564b1e67542efe0b8545dd481: Bug 1650049 [wpt PR 24422] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 00:30:03 +0000 - rev 541035
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1650049 [wpt PR 24422] - Update wpt metadata, a=testonly wpt-pr: 24422 wpt-type: metadata
30120c21b9c80e2e0e485e24f6abf6abc9f82418: Bug 1650049 [wpt PR 24422] - Python 3: port tests of content-type, http-cache, metadata, origin in …, a=testonly
ziransun <zsun@igalia.com> - Fri, 17 Jul 2020 11:12:46 +0000 - rev 541034
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1650049 [wpt PR 24422] - Python 3: port tests of content-type, http-cache, metadata, origin in …, a=testonly Automatic update from web-platform-tests Python 3: port tests of content-type, http-cache, metadata, origin in fetch (#24422) -- wpt-commits: ecd73dd12d21e70208f8917079be6f1baada0168 wpt-pr: 24422
5c05182cffc0a201a84c85eeb1341d80e7cdbd5b: Bug 1651773 [wpt PR 24536] - Reland: Abstract portal activation handling to avoid hack of making a fake promise., a=testonly
Jeremy Roman <jbroman@chromium.org> - Fri, 17 Jul 2020 11:12:41 +0000 - rev 541033
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651773 [wpt PR 24536] - Reland: Abstract portal activation handling to avoid hack of making a fake promise., a=testonly Automatic update from web-platform-tests Reland: Abstract portal activation handling to avoid hack of making a fake promise. This is somewhat verbose, but allows us to avoid the unhandled rejection being visible to script without having to make this hack even worse. Instead of actually calling activate(), this mirrors the spec structure by simply calling to underlying logic, passing a resolver where it makes sense and not (in this case, passing a substitute object) where it doesn't. The web test is added to SlowTests because it uses timeouts to check that things don't happen, and the additional test makes the timeouts 6 seconds total -- which is the test runner timeout. Slow tests get 5x longer before they are aborted. The alternative would have been to shorten the timeouts in this test, but that may have made the test more flaky. Bug: 1102081 Change-Id: Ied9d26e32ee426bf0a135279a9063f104d0e6460 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2290231 Commit-Queue: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> Reviewed-by: Adithya Srinivasan <adithyas@chromium.org> Auto-Submit: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#786912} -- wpt-commits: 12cef047ffeaec190bbe1e6ff363dcd70ecdc176 wpt-pr: 24536
b77633550e4e384fc53eb7594daf598dda0cedb6: Bug 1651763 [wpt PR 24534] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 09 Jul 2020 21:15:54 +0000 - rev 541032
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651763 [wpt PR 24534] - Update wpt metadata, a=testonly wpt-pr: 24534 wpt-type: metadata
fcc979d47133a093feb15be982bb17f86d84fe9e: Bug 1651763 [wpt PR 24534] - [LayoutNG] Only spanner siblings are considered adjacent., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 17 Jul 2020 11:12:31 +0000 - rev 541031
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651763 [wpt PR 24534] - [LayoutNG] Only spanner siblings are considered adjacent., a=testonly Automatic update from web-platform-tests [LayoutNG] Only spanner siblings are considered adjacent. The spec isn't crystal clear, but unconditionally considering spanners that are siblings of another spanner's ancestors as adjacent is definitely wrong. We need to resume column content layout inside the parent block of the spanner, since it may have a fixed block-size, block-end padding / border, or anything else that we'd just lose otherwise. This breaks one existing (non-WPT) test, but I'm not convinced that the test is valid. Filed crbug.com/1100849 for it. It also fixes 3 WPT tests. They were all quite complex, so I added a couple of simple ones, that demonstrate this fix more to the point. Bug: 829028 Change-Id: I9d55153f859dd84a5019e7d4dd09453f7f9ee1e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2290150 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#786841} -- wpt-commits: 90c4db31dd07db9c6009cdbc0358f460099a15fb wpt-pr: 24534
9d3da41a1b5dbe6034e9a034558864fb6995dec5: Bug 1651503 [wpt PR 24520] - [lint] Allow multiple --ignore-glob in `wpt lint`, a=testonly
Robert Ma <robertma@chromium.org> - Fri, 17 Jul 2020 11:12:26 +0000 - rev 541030
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651503 [wpt PR 24520] - [lint] Allow multiple --ignore-glob in `wpt lint`, a=testonly Automatic update from web-platform-tests [lint] Allow multiple --ignore-glob in `wpt lint` (#24520) -- wpt-commits: 17b665029472d57036e2ef0bab6767da339206d2 wpt-pr: 24520
4977aab203ddf3b50df33b6067e3af61f202bc0a: Bug 1651365 [wpt PR 24511] - [Taskcluster] Only schedule the sink-task for pull requests, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Fri, 17 Jul 2020 11:12:21 +0000 - rev 541029
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651365 [wpt PR 24511] - [Taskcluster] Only schedule the sink-task for pull requests, a=testonly Automatic update from web-platform-tests [Taskcluster] Only schedule the sink-task for pull requests (#24511) We don't need the sink-task for master pushes/etc, and this is a quick workaround for the fact that Taskcluster doesn't support >100 data dependencies (and we now schedule more than that for daily epoch runs!) In order to reliably test this behaviour, we now also ensure the ordering of tasks is deterministic. Co-authored-by: Robert Ma <robertma@chromium.org> -- wpt-commits: 821f177ada8d57dcec1f07327245c0a870c5758f wpt-pr: 24511
ae0e821895cd09f0b68a06bc619c5e9373cca1b8: Bug 1651523 [wpt PR 24522] - [LayoutNG] Only apply block-end margins where the block actually ends., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 17 Jul 2020 11:12:14 +0000 - rev 541028
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651523 [wpt PR 24522] - [LayoutNG] Only apply block-end margins where the block actually ends., a=testonly Automatic update from web-platform-tests [LayoutNG] Only apply block-end margins where the block actually ends. If we reached the end of a block in an earlier fragmentainer, but there's overflowing content, we'll revisit this block in subsequent fragmentainers as long as child content needs it. Repeating the block-end margins in these fragmentainers would be wrong, though. Use AdjustForFragmentation() only for margins, and rename it to AdjustMarginsForFragmentation(). The fieldset layout algorithm was using this one for borders/padding, while block and multicol layout called AdjustBorderScrollbarPaddingForFragmentation() in container_builder_. Become more uniform by calling that method for all in SetupFragmentBuilderForFragmentation() (via the base layout algorithm constructor). Since this depends on the initial fragment geometry being set, also do that in the base layout algorithm constructor. Bug: 829028 Change-Id: I6808d023e4e79ab489bdb3a48e3c6c47cf9db6c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2287313 Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#786791} -- wpt-commits: 931e5b7e2fe9818a7e15caa6378fabb00dbbca6a wpt-pr: 24522
af99b45ff92395ce309bb1bf80a1292f682b1914: Bug 1649571 [wpt PR 24400] - [WPT] Introduce a test-only-api helper script, a=testonly
Robert Ma <robertma@chromium.org> - Fri, 17 Jul 2020 11:12:09 +0000 - rev 541027
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1649571 [wpt PR 24400] - [WPT] Introduce a test-only-api helper script, a=testonly Automatic update from web-platform-tests [WPT] Introduce a test-only-api helper script including a helper function to load Mojo JS bindings. This will enable us to have better control over loading of *.mojom.js (notably disable automatic dependency loading) and reduce code duplication. Refactor WebXR tests to use this helper script, and add missing dependencies that were previously auto loaded. (WebUSB & WebBluetooth changes to follow.) Note that upstream WPT still does not have *.mojom.js available so tests will continue to fail there (but with a clearer error). Test results on Chromium waterfall should not change. Bug: 1094512 Change-Id: If660c4788c185bc7baf9ce6edbb691333e509d4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276652 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#786746} -- wpt-commits: 8d7104310d9fdb1b2eb6995219c31489d25010b5 wpt-pr: 24400
0629228bf2faad9e441bfbcb3480dc7549ea934b: Bug 1651435 [wpt PR 24514] - Actually remove six from Dockerfile, a=testonly
Robert Ma <robertma@chromium.org> - Fri, 17 Jul 2020 11:12:04 +0000 - rev 541026
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651435 [wpt PR 24514] - Actually remove six from Dockerfile, a=testonly Automatic update from web-platform-tests Actually remove six from Dockerfile With #24484 removing the dependency on system six, we are now able to remove it from the Docker image, which was introduced in #23733. Removing this has the benefit of avoiding introducing accidental dependency. -- wpt-commits: dea212bda34384982165966b6085dc9f4ec20858 wpt-pr: 24514
0ac3d8c2b179c58d512a7c8313d032f6ce713b73: Bug 1651023 [wpt PR 24483] - Python 3: port tests in common/security-features/subresource [part 1], a=testonly
Ziran Sun <zsun@igalia.com> - Fri, 17 Jul 2020 11:11:59 +0000 - rev 541025
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651023 [wpt PR 24483] - Python 3: port tests in common/security-features/subresource [part 1], a=testonly Automatic update from web-platform-tests Python 3: port tests in common/security-features/subresource [part 1] -- wpt-commits: 65017732a4d565590b4c350ef7d9ea476455c424 wpt-pr: 24483
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip