9342404bfd8228611c4d8a462aadb88f62825459: Bug 1588734 [wpt PR 19692] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 15 Oct 2019 14:37:47 +0000 - rev 499222
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588734 [wpt PR 19692] - Update wpt metadata, a=testonly wpt-pr: 19692 wpt-type: metadata
c250e091637dae76f6bf93dbc708916d43098fc1: Bug 1588734 [wpt PR 19692] - [css-writing-modes] Fix bug in wm-propagation-body-044.html, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Tue, 22 Oct 2019 09:45:23 +0000 - rev 499221
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588734 [wpt PR 19692] - [css-writing-modes] Fix bug in wm-propagation-body-044.html, a=testonly Automatic update from web-platform-tests [css-writing-modes] Fix bug in wm-propagation-body-044.html -- wpt-commits: 5804c2f857c5bbcd08441e997ab4d3d9f5f5086e wpt-pr: 19692
e68404adabd86de0cd2c01b27a7178967fc4728a: Bug 1587229 [wpt PR 19585] - Fix webdriver/tests/element_click/bubbling.py test_spin_event_loop, a=testonly
John Chen <johnchen0@outlook.com> - Tue, 22 Oct 2019 09:45:13 +0000 - rev 499220
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1587229 [wpt PR 19585] - Fix webdriver/tests/element_click/bubbling.py test_spin_event_loop, a=testonly Automatic update from web-platform-tests webdriver: fix test_spin_event_loop (#19585) Fixing an element_click test by scheduling the delayed function to execute right away. -- wpt-commits: 4b9b91843ea06b85b53b5e0c027f9b76cdc8fd85 wpt-pr: 19585
8f31c1a7574735440d661d95b4e7da50ba8b7e3e: Bug 1588729 [wpt PR 19691] - HTML: do not test IDL specifics in iframe load event test, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 22 Oct 2019 09:45:09 +0000 - rev 499219
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588729 [wpt PR 19691] - HTML: do not test IDL specifics in iframe load event test, a=testonly Automatic update from web-platform-tests HTML: do not test IDL specifics in iframe load event test (#19691) -- wpt-commits: 858fa42be06f4f4281f4b3f0c48e0f33b5676e89 wpt-pr: 19691
9a18540535ad6702b4041e6ffb7878afed860569: Bug 1588405 [wpt PR 19664] - Add tests for NFC API in non-visible document, a=testonly
kaixinjxq <xiuqix.jiang@intel.com> - Tue, 22 Oct 2019 09:45:04 +0000 - rev 499218
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588405 [wpt PR 19664] - Add tests for NFC API in non-visible document, a=testonly Automatic update from web-platform-tests Add tests for NFC API in non-visible document (#19664) -- wpt-commits: 9f31d497bf87bdf5ebc3ba70b5cb9f87786f4071 wpt-pr: 19664
7ac67c1d48410b22954b782e8fdb9652b9e7d081: Bug 1573199 [wpt PR 18390] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 15 Oct 2019 09:51:39 +0000 - rev 499217
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1573199 [wpt PR 18390] - Update wpt metadata, a=testonly wpt-pr: 18390 wpt-type: metadata
7537eb56a19a7d56862e2f37ef50fc7f4b3b0fd4: Bug 1573199 [wpt PR 18390] - Test that MediaQueryListener calls EventListener::handleEvent, a=testonly
Alexey Shvayka <shvaikalesh@gmail.com> - Tue, 22 Oct 2019 09:44:55 +0000 - rev 499216
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1573199 [wpt PR 18390] - Test that MediaQueryListener calls EventListener::handleEvent, a=testonly Automatic update from web-platform-tests Test that MediaQueryListener calls EventListener::handleEvent -- wpt-commits: 74286c98a9f403921e3d90af5b8693b437733ff8 wpt-pr: 18390
8001ebee1b76baa8a78fbe3398e708ba8541642f: Bug 1588701 [wpt PR 19687] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 15 Oct 2019 07:57:08 +0000 - rev 499215
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588701 [wpt PR 19687] - Update wpt metadata, a=testonly wpt-pr: 19687 wpt-type: metadata
c5647abbdcd3e98532ac6709a55c673509fcb234: Bug 1588701 [wpt PR 19687] - [LayoutNG] Allow negative margins to stay on the line after overflow, a=testonly
Koji Ishii <kojii@chromium.org> - Tue, 22 Oct 2019 09:44:47 +0000 - rev 499214
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588701 [wpt PR 19687] - [LayoutNG] Allow negative margins to stay on the line after overflow, a=testonly Automatic update from web-platform-tests [LayoutNG] Allow negative margins to stay on the line after overflow This patch allows atomic inlines to stay on the line even when it appears after the line overflowed, if its negative margins can bring the position back to inside of the line. This is not a well-defined behavior in the CSS spec, but legacy/WebKit/Gecko do this at some levels, though not really interoperable. Bug: 1001000 Change-Id: If8cfc5d51de14c8de6a9caa78fa10abaf6f1b5b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859424 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#705848} -- wpt-commits: eb78a40aac4a0072fd12585c7f29efde938a2e33 wpt-pr: 19687
3e9bce80c7ad590e42f47cb0832a157025814d7c: Bug 1588366 [wpt PR 19660] - [LayoutNG] Fix NGLineBreaker not to hang on negative margins, a=testonly
Koji Ishii <kojii@chromium.org> - Tue, 22 Oct 2019 09:44:43 +0000 - rev 499213
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588366 [wpt PR 19660] - [LayoutNG] Fix NGLineBreaker not to hang on negative margins, a=testonly Automatic update from web-platform-tests [LayoutNG] Fix NGLineBreaker not to hang on negative margins This patch fixes a case where |NGLineBreaker| loops infinitely when there is a negative margin. The case was a regression by r701601 (crrev.com/c/1826063). Handling combinations of a) trailable items, b) empty spans, and c) negative margins together is becoming more complex as we fix issues. This patch revises how we handle them. One of the complexities is open tags being ambiguous; e.g., this open tag is not trailable and thus breaks before it: <span>text but these open tags are trailable: <span> text <span></span>text <span> </span>text and it can even nest more, contain floating/out-of-flow objects, or have negative margins. Before this patch, |NGLineBreaker| tries to stop as early as possible, rewind, and consume trailable items. The last part (consuming trailable items) is scarly because rewind loops can occur if we try to rewind again. The new approach is to try to consume possibly trailable items before it rewinds, and avoids consuming after rewind. There might be cases where the new approach consumes more, but `blink_perf.layout` is neutral: https://pinpoint-dot-chromeperf.appspot.com/job/11fdf216c20000 In the test, case 2 and 5 fail in legacy, because the legacy behavior is based on a bug (crbug.com/979894) or the new behavior makes more sense, and the new behavior is interoperable with Edge/Gecko. Note, this change should be able to eliminate |kTrailable| state, and that eliminate consuming after rewind completely, but we still need it in a few places. It is for future patches to clean them up. Bug: 1011816 Change-Id: Ic915a26f1ee570ebe999ffbeee680659dcbd9789 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849737 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#705844} -- wpt-commits: d36a8bac6d6d0c14fa6d7475b6f06ffd26967b25 wpt-pr: 19660
2fc47e585a2d829a7ee1b066e2de1b604d928ee5: Bug 1588566 [wpt PR 19677] - The block-offset of a spanner may affect layout., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Tue, 22 Oct 2019 09:44:34 +0000 - rev 499212
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588566 [wpt PR 19677] - The block-offset of a spanner may affect layout., a=testonly Automatic update from web-platform-tests The block-offset of a spanner may affect layout. We already had code that copied to the block-offset from the spanner placeholder to the actual spanner layout object, but we also need to make sure that it actually gets laid out. See test: In the initial layout pass we'd set the block-size of the first column row (with the empty DIV) to the block-size of the multicol container. Then we'd bump into the spanner, and realize that this block-size wouldn't do, since we need to balance columns in front of a spanner. Because of this initial block-size of the column row, the initial layout pass of the spanner would put the spanner below that, tricking the machinery into believing that we need a break inside the spanner. In the next layout pass the block-size of the column row would be corrected, and also the position of the spanner. But we wouldn't re-lay out, and thus incorrectly keeping a pagination strut in the middle of the spanner. Bug: 1006249 Change-Id: If7ec10389ba5f6e78d9ecb5fd4ad7fd113c128bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859977 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#705646} -- wpt-commits: 20a55f606de85d95a46cd19b423c9215cb39898c wpt-pr: 19677
732a5510ef02fceea61880ba31e74d841fa1cabd: Bug 1588584 [wpt PR 19680] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 14 Oct 2019 20:51:45 +0000 - rev 499211
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588584 [wpt PR 19680] - Update wpt metadata, a=testonly wpt-pr: 19680 wpt-type: metadata
8791a2df27e774632f48cc422b3ca7b43f8d6e66: Bug 1588584 [wpt PR 19680] - Update interfaces/mediasession.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 22 Oct 2019 09:44:27 +0000 - rev 499210
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588584 [wpt PR 19680] - Update interfaces/mediasession.idl, a=testonly Automatic update from web-platform-tests Update interfaces/mediasession.idl (#19680) Source: https://github.com/tidoust/reffy-reports/blob/4d7ad55/ed/idl/mediasession.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/597780528 -- wpt-commits: 38c2e8d53c9e54f5c4a914d1528aff4e60f07cdf wpt-pr: 19680
a1fc432a134a7fa425bff017fb8140d18c79fec6: Bug 1587531 [wpt PR 19600] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 14 Oct 2019 20:28:25 +0000 - rev 499209
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1587531 [wpt PR 19600] - Update wpt metadata, a=testonly wpt-pr: 19600 wpt-type: metadata
48db767a35dd4e1bd86fd3e92b1025d1672c7f8e: Bug 1587531 [wpt PR 19600] - wake lock: Implement new proposed API., a=testonly
Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> - Tue, 22 Oct 2019 09:44:19 +0000 - rev 499208
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1587531 [wpt PR 19600] - wake lock: Implement new proposed API., a=testonly Automatic update from web-platform-tests wake lock: Implement new proposed API. This is another big update to the implementation, which now follows the API proposed in https://github.com/w3c/wake-lock/issues/226. From a Blink/Chromium internals perspective, things have not changed much, and we still perform the same permission checks and connect to the wake lock service via WakeLockStateRecord. The biggest change is that WakeLockController was merged into WakeLock itself. From an end-user perspective, though, the API now looks like a mix of the old, navigator-based API and the one we implemented a few months ago: * The main idea is that WakeLock.request() no longer returns a promise that does not resolve while the lock is held, as that is not very intuitive. Instead, it returns a new WakeLockSentinel object. * WakeLockSentinel is a new interface that can release() a lock and receive "release" events. * We do go back to a Navigator-based API, but we also support WorkerNavigator. * There is no WakeLockRequest interface or state tracking in the WakeLock interface. * WakeLock.requestPermission() was removed. * Consequently, we now have a WakeLockEvent interface. The changes to the spec still need to land, but there is some rough consensus on what the API should look like, and we do not want to miss the M79 branch cut. Bug: 257511, 1010162 Change-Id: If1baed914ccd9eb7103a1bb71a40529976777ec2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849683 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Cr-Commit-Position: refs/heads/master@{#705632} -- wpt-commits: 1a69ff8bc7a40d2e37ce0ce822e980a94bad9333 wpt-pr: 19600
3fd8b3cbde102e436a8acfbd9fab2aebbd9f3e9e: Bug 1588501 [wpt PR 19672] - Rewrite wpt/svg/animations/slider-switch.html to use 'begin' as trigger, a=testonly
Fredrik Söderquist <fs@opera.com> - Tue, 22 Oct 2019 09:44:14 +0000 - rev 499207
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588501 [wpt PR 19672] - Rewrite wpt/svg/animations/slider-switch.html to use 'begin' as trigger, a=testonly Automatic update from web-platform-tests Rewrite wpt/svg/animations/slider-switch.html to use 'begin' as trigger The interval timer could end up racing with the animation update timer, meaning that the new animation values had not yet been applied when the |retries| counter reached zero and the assertions were made. Refactor the test to trigger the next "action" (new pair of clicks or checking the result) when one of the timed elements listening on the "b.click" event has begun. Also change |retries| into counting how many clicks are remaining (rather than how many interval timer firings). Bug: 1013736 Change-Id: I374cb9c499ca18a791f76dabcb1db8bcd6f38461 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1859955 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#705574} -- wpt-commits: c7abd94317e9a039ee0a93324571e94b91a9ab09 wpt-pr: 19672
67c1c14f74813f9c99efc0df1493c1bd888e8fa5: Bug 1588529 [wpt PR 19676] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 14 Oct 2019 19:02:21 +0000 - rev 499206
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588529 [wpt PR 19676] - Update wpt metadata, a=testonly wpt-pr: 19676 wpt-type: metadata
1409177f93c25ee656e46d54152fe721fab9b4c2: Bug 1588529 [wpt PR 19676] - Test empty script elements, a=testonly
Rob Buis <rbuis@igalia.com> - Tue, 22 Oct 2019 09:44:06 +0000 - rev 499205
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588529 [wpt PR 19676] - Test empty script elements, a=testonly Automatic update from web-platform-tests Test empty script elements (#19676) * Test empty script elements -- wpt-commits: b9b9fb904eff219906f7f9a5742c8215d5e65ec8 wpt-pr: 19676
eeb1834f5148a5dfea3b0d2ba15087c7e3482de2: Bug 1588190 [wpt PR 19647] - [docs] Include wptrunner docs on web-platform-tests.org, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Tue, 22 Oct 2019 09:44:01 +0000 - rev 499204
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1588190 [wpt PR 19647] - [docs] Include wptrunner docs on web-platform-tests.org, a=testonly Automatic update from web-platform-tests [docs] Document wptrunner classes These classes are referenced from the ReStructuredText-formatted documentation. -- [docs] Fix build process for wptrunner The Mozilla-provided "intersphinx" metadata does not include an entry for the "mozlog" module. Replace the rST cross-referencing roles with a hyperlink to the documentation webpage. -- [docs] Integrate wptrunner documentation -- [docs] Remove wptrunner-specific tooling -- [docs] Remove outdated content -- [docs] Consolidate info on expectations files -- [docs] Expose a single index for wptrunner docs -- wpt-commits: 61adf1dd0f37b016ce851722c2f3045560c899e1, 1a6f43365b8230df3b25ed28627802199e618b30, 355db3e8653970fab13c78fee743eee667be6025, f5c837e32ff3961266ba76febda0e9b9f520a28e, 94a9a8f0d9520932ffbda2ad6ff7dfcab144979f, 197f2cf0b343f17dc3f0d85b33cdcc62039d9421, 6ffed675082f1faae9b1ca16908efbb333c43dbd wpt-pr: 19647
bf4da65a25220382da8e5a334b0c99392a676b42: Bug 1587871 [wpt PR 19626] - Regenerate pregenerated certs, a=testonly
Sam Sneddon <me@gsnedders.com> - Tue, 22 Oct 2019 09:43:56 +0000 - rev 499203
Push 36736 by malexandru@mozilla.com at Sat, 26 Oct 2019 22:18:59 +0000
Bug 1587871 [wpt PR 19626] - Regenerate pregenerated certs, a=testonly Automatic update from web-platform-tests Regenerate pregenerated certs We've needed to do this since 2cccd822f95, but haven't. Whoops. This also stops outputting the text form of the certificate before the PEM header as macOS/iOS's Security.framework only scans the first 8192 characters for the beginning of the header. -- Readd documentation on how to generate pregenerated certs This accidentally got removed in afd4200510. -- wpt-commits: 49d6007b38f818f208f672f106f2388db7ff10d8, b88d541c8cc7868ad6b9eefab4949602d826afbe wpt-pr: 19626
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip