b76caf562e12410cd6c5213c607f525de2a77b00: Bug 1457485 [wpt PR 10686] - HTML: document.open() event listener removal, a=testonly draft
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:22:44 +0000 - rev 791487
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457485 [wpt PR 10686] - HTML: document.open() event listener removal, a=testonly Automatic update from web-platform-testsHTML: document.open() event listener removal For https://github.com/whatwg/html/pull/3653. -- wpt-commits: 923d852c61cb50cb3be540dcbf54f2d5ec1518e1 wpt-pr: 10686
d4349e97e7798f3dddb3d4d40feb8eaf01bac9d9: Bug 1458519 [wpt PR 10759] - Add old-tests/OWNERS, a=testonly draft
Simon Pieters <zcorpan@gmail.com> - Thu, 03 May 2018 22:21:27 +0000 - rev 791486
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458519 [wpt PR 10759] - Add old-tests/OWNERS, a=testonly Automatic update from web-platform-testsAdd old-tests/OWNERS (#10759) -- wpt-commits: a7a988cbb5edb58b50f200a66057a0d5620209a8 wpt-pr: 10759
fb8185481d7a1322c6aaadd16f69af29e0855dff: Bug 1457947 [wpt PR 10713] - [css-grid] Subtract scrollbar in ComputeReplacedLogicalHeightUsing(), a=testonly draft
Manuel Rego Casasnovas <rego@igalia.com> - Thu, 03 May 2018 22:20:02 +0000 - rev 791485
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457947 [wpt PR 10713] - [css-grid] Subtract scrollbar in ComputeReplacedLogicalHeightUsing(), a=testonly Automatic update from web-platform-tests[css-grid] Subtract scrollbar in ComputeReplacedLogicalHeightUsing() In LayoutBox::ComputeReplacedLogicalHeightUsing() we were using the OverrideContentLogicalHeight() plus scrollbar height, that was wrong and we should subtract the scrollbar too. This caused issues to resolve the percentage heights on grid item replaced children, if the grid item has a scrollbar. To fix the issue we just need to follow the suggestion in the TODO and use OverrideContentLogicalHeight() directly. This was the last place using OverrideContentAndScrollbarLogicalHeight() so we can get rid of it. The patch removes that method together with OverrideContentAndScrollbarLogicalWidth() that was no longer used. BUG=837141 TEST=external/wpt/css/css-grid/grid-items/percentage-size-replaced-subitems-001.html Change-Id: I28cf6e65c21e6314808c4430515f06c07d4a739e Reviewed-on: https://chromium-review.googlesource.com/1035003 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#554834} -- wpt-commits: 538eedafb15733c6113b44998170a6bbdae7518b wpt-pr: 10713
af07381c0e14e8845f5a515dd6879d099dd44b83: Bug 1458533 [wpt PR 10765] - Remove unused css-mode argument to the lint., a=testonly draft
Ms2ger <Ms2ger@gmail.com> - Thu, 03 May 2018 22:18:47 +0000 - rev 791484
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458533 [wpt PR 10765] - Remove unused css-mode argument to the lint., a=testonly Automatic update from web-platform-testsRemove unused css-mode argument to the lint. (#10765) -- wpt-commits: 615504bd195b931a43a7a2ba6403c67dd29bdfd7 wpt-pr: 10765
d95624a779c2505c3af7872e4a31e37574aae256: Bug 1458055 [wpt PR 10715] - Cleanup CSSOM View interfaces test, a=testonly draft
Chris Nardi <christopherncarmel@hotmail.com> - Thu, 03 May 2018 22:17:30 +0000 - rev 791483
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458055 [wpt PR 10715] - Cleanup CSSOM View interfaces test, a=testonly Automatic update from web-platform-testsCleanup CSSOM View interfaces test The CSSOM View interfaces test added the Geometry IDL as untested, but it is never needed (removing it does not affect test results). Removing it means that less IDL needs to be parsed, speeding up the test. The test also adds Document as an object twice, and refers to the CSSOM spec instead of the CSSOM View spec. This change fixes both of these issues as well. -- wpt-commits: dce95ec0d867129a8f4810330b473eca3e515cea wpt-pr: 10715
0c43fa8e9d815a1652e592fdccbd3f92d689e68b: Bug 1457687 [wpt PR 10703] - Update wpt metadata, a=testonly draft
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 03 May 2018 16:51:02 +0000 - rev 791482
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457687 [wpt PR 10703] - Update wpt metadata, a=testonly wpt-pr: 10703 wpt-type: metadata
5d5c17fa838749610f9134086bef6b0ab2b2da07: Bug 1457687 [wpt PR 10703] - Correct document.domain setter test, a=testonly draft
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:16:09 +0000 - rev 791481
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457687 [wpt PR 10703] - Correct document.domain setter test, a=testonly Automatic update from web-platform-testsCorrect document.domain setter test Fixes #10695. -- wpt-commits: a13c9f65c007ddde78fe6c99c0f173dbc87cd245 wpt-pr: 10703
23f954677dc29584c89cd8c0d3debbc1433079a5: Bug 1457845 [wpt PR 10709] - Update wpt metadata, a=testonly draft
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 30 Apr 2018 10:35:28 +0000 - rev 791480
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457845 [wpt PR 10709] - Update wpt metadata, a=testonly wpt-pr: 10709 wpt-type: metadata
ed6953d839ef5d9835bc57c9952266273f372c6b: Bug 1457845 [wpt PR 10709] - Fetch: cleanup api/redirect, a=testonly draft
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:14:47 +0000 - rev 791479
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457845 [wpt PR 10709] - Fetch: cleanup api/redirect, a=testonly Automatic update from web-platform-testsFetch: cleanup api/redirect -- wpt-commits: 27a3aebab97421d95a14c7fd7b3d051773cfd199 wpt-pr: 10709
08e8a7ddb45ad47d4eba899cd5aa3d0a79dea442: Bug 1457844 [wpt PR 10708] - Update wpt metadata, a=testonly draft
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 30 Apr 2018 10:17:44 +0000 - rev 791478
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457844 [wpt PR 10708] - Update wpt metadata, a=testonly wpt-pr: 10708 wpt-type: metadata
4ba435f41414dbfb441f88979db6c1a7401963ec: Bug 1457844 [wpt PR 10708] - Fetch: fix and cleanup api/cors, a=testonly draft
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:13:26 +0000 - rev 791477
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457844 [wpt PR 10708] - Fetch: fix and cleanup api/cors, a=testonly Automatic update from web-platform-testsFetch: fix and cleanup api/cors cors-multiple-origins went against the specification and required support for multiple origins listed in Access-Control-Allow-Origin. -- wpt-commits: e47396d5c643c6a0bc4782045a8cc77233df3514 wpt-pr: 10708
81273ed15d357b8c0db8ae8e7cbeccf54e445f24: Bug 1458107 [wpt PR 10725] - [LayoutNG] Improve handling of adjoining floats., a=testonly draft
Morten Stenshorne <mstensho@chromium.org> - Thu, 03 May 2018 22:12:07 +0000 - rev 791476
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458107 [wpt PR 10725] - [LayoutNG] Improve handling of adjoining floats., a=testonly Automatic update from web-platform-tests[LayoutNG] Improve handling of adjoining floats. A float always needs to be positioned by its block parent, so passing them around to children, parents or siblings really shouldn't be necessary (and it *was* somewhat confusing, since nobody but the direct float parent is allowed to touch them anyway, apart from placing them into temporary exclusion spaces). The main reason for passing them around like that, was for other blocks to determine, based on the list of floats being empty or not, the need for relayout once the BFC offset was resolved. Instead, confine the list of unpositioned floats to the block parent of those floats, and introduce the concept of adjoining float types (none, left, right, both). Adjoining floats occur when the BFC offset is unknown, meaning that their position may be affected by the current layout algorithm. Adjoining float types will now be the thing that's both input to and output from the layout algorithms. Having something other than "none" means that a block's BFC offset is unknown, but that doesn't automatically mean that we have to abort and re-layout if the BFC offset gets resolved. If the "floats BFC offset" is known, for instance, those adjoining floats may be positioned right away. Still we need to know about them (positioned or not), to get clearance correct. We're going to need to treat adjoining floats specially when applying clearance. Will deal with that in a later CL. For now, we just keep track of the adjoining float types, so that the clearance machinery can tell that there are floats there that may not yet be positioned. That used to be taken care of the list of unpositioned floats, but, as previously stated, adjoining floats are special, and we need to know about them, whether they are positioned or not. This is a preparatory CL for that. Each time we add an unpositioned float, we need to update the types of adjoining floats, so that these can be returned from the algorithm if necessary. Whether they end up being positioned right away or not isn't relevant. Adjoining is adjoining. Note that we don't have to #include the header file for unpositioned floats as much as before now, but I'll clean that up in a follow-up CL, because it turned out that there were quite a few translation units that got stuff for free via that header file, instead of explicitly including what they need. Had to rewrite how we deal with floats in HandleNewFormattingContext() and LayoutNewFormattingContext(), since those depended on a list of all preceding unpositioned floats to place them into a temporary exclusion space, to figure out whether to let the child's margin be adjoining with the current margin strut or not. Instead of using a temporary exclusion space, we now position floats via the regular mechanisms, and initially assume that the child's margin is going to be adjoining. This means that we have to abort and roll back if there are preceding unpositioned floats. This is no different from how we lay out regular blocks, though. What *is* different is that if it turns out that the child's margin has to be separated from the strut, we'll have to abort and roll back once *again* (but only once). The algorithms now need to keep track of whether they need to abort if the BFC offset *changes*, rather than if it is *resolved*. We only allow the offset to resolve and optionally change *once* afterwards, though. Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ie527d659213049f180ebedc764e1d7f4926a5876 Reviewed-on: https://chromium-review.googlesource.com/1030191 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#555314} -- wpt-commits: 39563cf141605683bb8d76abb74eaa0c764d6c65 wpt-pr: 10725
e3f44fc7a4487d271ec684597371078e6155ad3c: Bug 1457656 [wpt PR 10700] - Parsing tests for CSS UI Level 3, a=testonly draft
Eric Willigers <ewilligers@users.noreply.github.com> - Thu, 03 May 2018 22:10:50 +0000 - rev 791475
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1457656 [wpt PR 10700] - Parsing tests for CSS UI Level 3, a=testonly Automatic update from web-platform-testsMerge pull request #10700 from ewilligers/css-ui3-parsing Parsing tests for CSS UI Level 3 -- wpt-commits: c83c53e0cc5ec8a7427c8039e772a3bbf1bb9f50 wpt-pr: 10700
14936c4de44f7a9ac8e06b2f13e400f928ee5763: Bug 1458286 [wpt PR 10737] - Disable kerning in wpt/css/CSS2/floats-clear/floats-143.xht, a=testonly draft
Koji Ishii <kojii@chromium.org> - Thu, 03 May 2018 22:09:24 +0000 - rev 791474
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458286 [wpt PR 10737] - Disable kerning in wpt/css/CSS2/floats-clear/floats-143.xht, a=testonly Automatic update from web-platform-testsDisable kerning in wpt/css/CSS2/floats-clear/floats-143.xht This patch fixes wpt/css/CSS2/floats-clear/floats-143.xht not to rely on kerning table. This test has "PA" and "SS" in two different floats, assuming either of the below is true: a. The font does not have a kerning pair between "A" and "S". b. UA applies kerning across two different floats. This patch changes this test not to rely on these conditions. This fix is another test fix needed for CL:1022191. Change-Id: I78ea57b619fd08a9d671d507ebbb005b556fc183 Reviewed-on: https://chromium-review.googlesource.com/1036825 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#555066} -- wpt-commits: fe5aaaf49f48a36dd468213e00734725109d7b90 wpt-pr: 10737
683a54a77b2c9dbe259d45d53f46d1870f10936d: Bug 1458290 [wpt PR 10738] - Update wpt metadata, a=testonly draft
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 01 May 2018 20:48:36 +0000 - rev 791473
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458290 [wpt PR 10738] - Update wpt metadata, a=testonly wpt-pr: 10738 wpt-type: metadata
9c6d2da7af9b2baacd0ae50fa3a9dbd55c403303: Bug 1458290 [wpt PR 10738] - Move AudioParam tests to WPT, a=testonly draft
Raymond Toy <rtoy@chromium.org> - Thu, 03 May 2018 22:08:02 +0000 - rev 791472
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458290 [wpt PR 10738] - Move AudioParam tests to WPT, a=testonly Automatic update from web-platform-testsMove AudioParam tests to WPT Move many but not all WebAudio AudioParam tests to WPT. The criteria was whether Firefox passed the tests or, if not, the errors are actually bugs in Firefox. Most of the failures are because Firefox threw the wrong type of error. We also skipped over most of the tests that use offline.suspend(). Bug: 745778 Change-Id: If4755089938ddf1b9825faa3392d1d10e3b9293f Reviewed-on: https://chromium-review.googlesource.com/1036456 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#555140} -- wpt-commits: 575c6d120e84e2dd1343bd42c95f7d6b2477c12a wpt-pr: 10738
068327d87b6a4597ef218422b143c1f81484ab85: Bug 1458313 [wpt PR 10739] - Revert "Update mozrunner from 7.0.0 to 7.0.1", a=testonly draft
Geoffrey Sneddon <me@gsnedders.com> - Thu, 03 May 2018 22:06:43 +0000 - rev 791471
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458313 [wpt PR 10739] - Revert "Update mozrunner from 7.0.0 to 7.0.1", a=testonly Automatic update from web-platform-testsRevert "Update mozrunner from 7.0.0 to 7.0.1" (#10739) This reverts commit 8b9f853fd06ca887b340e77e342d323c32635a13 See https://github.com/w3c/web-platform-tests/issues/10736 -- wpt-commits: 11181545aa1e4d3e1e2f00fbedb8d048af091e83 wpt-pr: 10739
694d61e6af81bd2ff56ee930babfa654245cc3d7: Bug 1448567 [wpt PR 10166] - Add alternate_hosts, a=testonly draft
Geoffrey Sneddon <me@gsnedders.com> - Thu, 03 May 2018 22:05:27 +0000 - rev 791470
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1448567 [wpt PR 10166] - Add alternate_hosts, a=testonly Automatic update from web-platform-testsFix #2669: Add alternate_hosts (#10166) -- wpt-commits: dfeea56c848137e18c75e1f931f4b3e1497ea61b wpt-pr: 10166
f609cb03efd5b483d1c01c03e16812cf337bc4b7: Bug 1458094 [wpt PR 10721] - Update wpt metadata, a=testonly draft
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 01 May 2018 15:19:23 +0000 - rev 791469
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458094 [wpt PR 10721] - Update wpt metadata, a=testonly wpt-pr: 10721 wpt-type: metadata
1706d5264917db985dc44550ee9c3b7172baf8f0: Bug 1458094 [wpt PR 10721] - Update mozrunner to 7.0.1, a=testonly draft
pyup-bot <github-bot@pyup.io> - Thu, 03 May 2018 22:04:07 +0000 - rev 791468
Push 108825 by bmo:james@hoppipolla.co.uk at Fri, 04 May 2018 14:12:31 +0000
Bug 1458094 [wpt PR 10721] - Update mozrunner to 7.0.1, a=testonly Automatic update from web-platform-testsUpdate mozrunner from 7.0.0 to 7.0.1 -- wpt-commits: 8b9f853fd06ca887b340e77e342d323c32635a13 wpt-pr: 10721
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip