f7787426d7de95c0499d4bbfb9904968d380f6df: Bug 1515915 [wpt PR 14632] - Add new Feature-Policy-Report-Only header, a=testonly
Ian Clelland <iclelland@chromium.org> - Thu, 31 Jan 2019 13:51:25 +0000 - rev 457663
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515915 [wpt PR 14632] - Add new Feature-Policy-Report-Only header, a=testonly Automatic update from web-platform-tests Add new Feature-Policy-Report-Only header This removes the special parsing for "-report-only" features, and replaces it with the new "Feature-Policy-Report-Only" header, as noted in the explainer. (https://github.com/WICG/feature-policy/blob/master/reporting.md) Tests are updated for the new behaviour. Bug: 916233 Change-Id: Idc87e377123c618240ebf1186f7e68901d9fcbeb Reviewed-on: https://chromium-review.googlesource.com/c/1378235 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#618685} -- wpt-commits: 82c3ea4fb290ae6e8d3aa671c888e3f224a59f89 wpt-pr: 14632
0dce2dbf5681cd425eaacef56181be2f78a4c696: Bug 1516140 [wpt PR 14651] - [Azure Pipelines] Use raw URL with `brew cask install`, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 31 Jan 2019 13:51:23 +0000 - rev 457662
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1516140 [wpt PR 14651] - [Azure Pipelines] Use raw URL with `brew cask install`, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Use raw URL with `brew cask install` (#14651) Due to caching at some level, Safari TP on Azure Pipelines is still release 70, although it should now be 72: https://github.com/Homebrew/homebrew-cask-versions/pull/6747 Use raw URL for Chrome + Firefox too. -- wpt-commits: ac06ab662bf97c4e06feecd888225708521baa33 wpt-pr: 14651
c2ce9f6d4bd683b59fee926f5b6d8b6747656db0: Bug 1516109 [wpt PR 14646] - Use get-host-info to run fetch/abort test in CI, a=testonly
youennf <youennf@users.noreply.github.com> - Thu, 31 Jan 2019 13:51:21 +0000 - rev 457661
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1516109 [wpt PR 14646] - Use get-host-info to run fetch/abort test in CI, a=testonly Automatic update from web-platform-tests Use get-host-info to run in CI. Use method.py to get a response without any body (#14646) -- wpt-commits: f3cbe0368c46f52a1d8145181db4d1e4e6afc123 wpt-pr: 14646
973dce2ed4ca1dcf639636b6d2faf2fcc3bf3233: Bug 1516086 [wpt PR 14641] - Log where we are downloading Firefox from, a=testonly
James Graham <james@hoppipolla.co.uk> - Thu, 31 Jan 2019 13:51:18 +0000 - rev 457660
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1516086 [wpt PR 14641] - Log where we are downloading Firefox from, a=testonly Automatic update from web-platform-tests Log where we are downloading Firefox from To make logging in the browser class work better we explicitly pass in a logger, rather than depending on a global variable. -- wpt-commits: bc34f4b379c760a5851d65689c88398d309dcf64 wpt-pr: 14641
a1cb20fc03ed9e01213b13ae5296bc68d2c00d91: Bug 1516084 [wpt PR 14640] - [Background Fetch] Remove use of chromium specific resource, a=testonly
Rayan Kanso <rayankans@chromium.org> - Thu, 31 Jan 2019 13:51:11 +0000 - rev 457659
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1516084 [wpt PR 14640] - [Background Fetch] Remove use of chromium specific resource, a=testonly Automatic update from web-platform-tests [Background Fetch] Remove use of chromium specific resource Change-Id: If2d7b8d47fe3ed3c5b0458e8166ae2409e3337db Reviewed-on: https://chromium-review.googlesource.com/c/1388467 Reviewed-by: Mugdha Lakhani <nator@chromium.org> Commit-Queue: Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#618521} -- wpt-commits: 08a84e5a8c875e4aa2dad40759a5069d440eae84 wpt-pr: 14640
ed3d433da2b64d6e0af3a46a5f5f597a0ffd4239: Bug 1516067 [wpt PR 8624] - Add HTMLInputElement select event test, a=testonly
kaixinjxq <xiuqix.jiang@intel.com> - Thu, 31 Jan 2019 13:51:09 +0000 - rev 457658
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1516067 [wpt PR 8624] - Add HTMLInputElement select event test, a=testonly Automatic update from web-platform-tests Add HTMLInputElement select event test (#8624) * Add HTMLInputElement select event test * Address @jdm's comments -- wpt-commits: 0c17bdc23f7e57994452fc669f6d0bcd371299d1 wpt-pr: 8624
900ad7c0f0ac573d34a1a210a69e0c2a5c9ed15c: Bug 1515853 [wpt PR 14622] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 23 Dec 2018 03:34:39 +0000 - rev 457657
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515853 [wpt PR 14622] - Update wpt metadata, a=testonly wpt-pr: 14622 wpt-type: metadata
770d7f4f402f58bcffd84d4f0c2eaee639ce78f3: Bug 1515853 [wpt PR 14622] - [Background Fetch] Display upload progress., a=testonly
Rayan Kanso <rayankans@chromium.org> - Thu, 31 Jan 2019 13:51:03 +0000 - rev 457656
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515853 [wpt PR 14622] - [Background Fetch] Display upload progress., a=testonly Automatic update from web-platform-tests [Background Fetch] Display upload progress. Use the progress updates from the DS, and make sure the registration displays accurate information with regards to uploads. Bug: 774054 Change-Id: Iccec2e61310442c051339505c2397bbaa244b50c Reviewed-on: https://chromium-review.googlesource.com/c/1386865 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#618515} -- wpt-commits: 9f99e81b2d827b50f5a97478a0d79a064cb99d5a wpt-pr: 14622
89109a138dd8db16a1b7303e78dbcb55713b460f: Bug 1516087 [wpt PR 14642] - Add firefox buildid and source changeset to wptreport.json, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 31 Jan 2019 13:41:01 +0000 - rev 457655
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1516087 [wpt PR 14642] - Add firefox buildid and source changeset to wptreport.json, a=testonly Automatic update from web-platform-tests Add firefox buildid and source changeset to wptreport.json This adds two keys to the run_info dict for Firefox; browser_build_id containing a build id and browser_changeset containing the SHA1 of the source commit from which the browser was built. -- wpt-commits: f12cd12fea9e577e4d18b8f3599c0e359abc0038 wpt-pr: 14642
815e350219098d966c5a9c88b84b674d292dfff8: Bug 1515892 [wpt PR 14626] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 22 Dec 2018 10:59:26 +0000 - rev 457654
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515892 [wpt PR 14626] - Update wpt metadata, a=testonly wpt-pr: 14626 wpt-type: metadata
c8af325c4532dbc41b12e14c2ab831c134322e05: Bug 1515892 [wpt PR 14626] - Move 'contain: size' handling for replaced content, a=testonly
Fredrik Söderquist <fs@opera.com> - Thu, 31 Jan 2019 12:14:34 +0000 - rev 457653
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515892 [wpt PR 14626] - Move 'contain: size' handling for replaced content, a=testonly Automatic update from web-platform-tests Move 'contain: size' handling for replaced content For Legacy layout, hoist the check for size containment out to ComputeIntrinsicSizingInfoForReplacedContent, since this is the "real" entrypoint. For NG, put the check in NGLayoutInputNode::IntrinsicSize. This also makes ComputeIntrinsicSizingInfo slightly more focused on computing the intrinsic dimensions, and avoids calling it at all if the box is subject to size containment. Bug: 917018 Change-Id: I0e3fdc48e9c5a104cadaa253cb7cef23fdc42ece Reviewed-on: https://chromium-review.googlesource.com/c/1386849 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#618496} -- wpt-commits: 14cf574d6d8ff4d5ddd116dcb117dacaae6d0d6d wpt-pr: 14626
4acf41d59c72657ae06c000b71199f8b8de1af17: Bug 1514958 [wpt PR 14577] - Plumbing border box through to viz, and adding clip rect to backdrop-filter, a=testonly
Mason Freed <masonfreed@chromium.org> - Thu, 31 Jan 2019 12:14:30 +0000 - rev 457652
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1514958 [wpt PR 14577] - Plumbing border box through to viz, and adding clip rect to backdrop-filter, a=testonly Automatic update from web-platform-tests Plumbing border box through to viz, and adding clip rect to backdrop-filter With this CL, the border box of the element containing backdrop-filter is plumbed through to viz, so that the backdrop-filter effect can be properly clipped at the border box of the element itself. This will keep it from "bleeding" outside to the border rect of the entire layer (including children). This should fix most of the reported bugs related to the filtered effect extending beyond the proper bounds. Bug: 497522, 813796, 767997, 659501, 632979, 618913, 593307 Change-Id: I5f24ac79053b3779cea128aacabd60f9d66702f4 Reviewed-on: https://chromium-review.googlesource.com/c/1378811 Reviewed-by: Michael Wasserman <msw@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#618358} -- wpt-commits: e95a36a608508cafe6739bda57ba405cc03e04d5 wpt-pr: 14577
603e8e8097b742115dca2e195f59f65618b97ac0: Bug 1523562 [wpt PR 14417] - Update RTCPeerConnection-helper.js, a=testonly
youennf <youennf@users.noreply.github.com> - Thu, 31 Jan 2019 12:14:28 +0000 - rev 457651
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14417] - Update RTCPeerConnection-helper.js, a=testonly Automatic update from web-platform-tests Update RTCPeerConnection-helper.js (#14417) * Update RTCPeerConnection-helper.js according changes proposed in https://github.com/web-platform-tests/wpt/pull/13499 * Modernize doSignalingHandshake -- wpt-commits: b75b876e7d5843582f21e5b52c54d509dffb6da0 wpt-pr: 14417
91f314cf9ea056321628ded8ad618d36bca9b6ff: Bug 1523562 [wpt PR 14607] - Sync Mozilla CSS tests as of 2018-12-19, a=testonly
L. David Baron <dbaron@dbaron.org> - Thu, 31 Jan 2019 12:14:26 +0000 - rev 457650
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14607] - Sync Mozilla CSS tests as of 2018-12-19, a=testonly Automatic update from web-platform-tests Sync Mozilla CSS tests as of 2018-12-20 (#14607) Sync Mozilla CSS tests as of https://hg.mozilla.org/mozilla-central/rev/49be2c1eb4c8c64cadd4297ff9eb5454f4bb4a93 . This contains changes from [bug 1322780](https://bugzilla.mozilla.org/show_bug.cgi?id=1322780) by @BorisChiou, reviewed by @dholbert. -- wpt-commits: 8b2ce21a53705a0ac50ae66824be2229eb114579 wpt-pr: 14607
861de58e5a3d7f16f790e245d90f89e8c5dd455c: Bug 1515858 [wpt PR 14623] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 22 Dec 2018 07:44:41 +0000 - rev 457649
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515858 [wpt PR 14623] - Update wpt metadata, a=testonly wpt-pr: 14623 wpt-type: metadata
e820da6c7a2e8b6a9d20eb4dc0bddf2c4e763035: Bug 1515858 [wpt PR 14623] - [LayoutNG] Don't allow line height quirk inside list items., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 31 Jan 2019 12:14:21 +0000 - rev 457648
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515858 [wpt PR 14623] - [LayoutNG] Don't allow line height quirk inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See https://github.com/whatwg/quirks/issues/38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623
090bc023df087e98a88d43d499982b2c32f1f154: Bug 1515539 [wpt PR 14609] - WPT for passive document level wheel event listeners., a=testonly
Sahel Sharify <sahel@chromium.org> - Thu, 31 Jan 2019 12:14:19 +0000 - rev 457647
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515539 [wpt PR 14609] - WPT for passive document level wheel event listeners., a=testonly Automatic update from web-platform-tests WPT for passive document level wheel event listeners. This cl adds a WPT test for passive document level wheel event listeners intervention. It also adds a message to let developers know when they call preventDefault on wheel events that are non-cancelable due to the intervention. Bug: 626196 Change-Id: I7f51ff4560de7ffa7bf89cab9e5332daa6cb70c0 Reviewed-on: https://chromium-review.googlesource.com/c/1383323 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#618297} -- wpt-commits: a2448c2392587668a9b9f8ec4e3d0dec76640f25 wpt-pr: 14609
7bffd692126e44ed1526fe89bcec09fe000bc788: Bug 1515866 [wpt PR 14624] - Don't create a logging output element until we have DOMContentLoaded, a=testonly
James Graham <james@hoppipolla.co.uk> - Thu, 31 Jan 2019 12:14:17 +0000 - rev 457646
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515866 [wpt PR 14624] - Don't create a logging output element until we have DOMContentLoaded, a=testonly Automatic update from web-platform-tests Don't create a logging output element until we have DOMContentLoaded Otherwise running with logs enabled can implicitly create a document.body that can change the results of tests. -- wpt-commits: dfa78e227367066b18b0bbc863e0ad8e86a1b40d wpt-pr: 14624
c9977634d74483cb22b6f7a816d201d1784d097f: Bug 1515894 [wpt PR 14627] - Update mozlog to 3.10, a=testonly
pyup-bot <github-bot@pyup.io> - Thu, 31 Jan 2019 12:14:15 +0000 - rev 457645
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515894 [wpt PR 14627] - Update mozlog to 3.10, a=testonly Automatic update from web-platform-tests Update mozlog from 3.9 to 3.10 -- wpt-commits: daf2be33441ef2ed723b2d9816f4fb1db795f49a wpt-pr: 14627
1d07a9197385fd05cb29eecd4104c6392653ec0a: Bug 1515895 [wpt PR 14628] - Update mozleak to 0.2, a=testonly
pyup-bot <github-bot@pyup.io> - Thu, 31 Jan 2019 12:14:13 +0000 - rev 457644
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1515895 [wpt PR 14628] - Update mozleak to 0.2, a=testonly Automatic update from web-platform-tests Update mozleak from 0.1 to 0.2 -- wpt-commits: 2deb1349ebe32b2e5046c3f41b570a079e3092a0 wpt-pr: 14628
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip