fba7111c2a99bbb1fda4b7a2db46498b801c7dcb: Bug 1457687 [wpt PR 10703] - Correct document.domain setter test, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:16:09 +0000 - rev 474111
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
c469e4b4995d2daa6408ce9bb55f12b2c887100d: Bug 1457845 [wpt PR 10709] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 30 Apr 2018 10:35:28 +0000 - rev 474110
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1457845 [wpt PR 10709] - Update wpt metadata, a=testonly wpt-pr: 10709 wpt-type: metadata
9debd5451211af584ffb5452e8f72988df369840: Bug 1457845 [wpt PR 10709] - Fetch: cleanup api/redirect, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:14:47 +0000 - rev 474109
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
e326893d154e59f0b211c5cefb62b68ceefed1bf: Bug 1457844 [wpt PR 10708] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 30 Apr 2018 10:17:44 +0000 - rev 474108
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1457844 [wpt PR 10708] - Update wpt metadata, a=testonly wpt-pr: 10708 wpt-type: metadata
2c70e7546c82799b1a160966c9af9df0ac75db76: Bug 1457844 [wpt PR 10708] - Fetch: fix and cleanup api/cors, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Thu, 03 May 2018 22:13:26 +0000 - rev 474107
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
812315117087c0015507ae105889c857129361d2: Bug 1458107 [wpt PR 10725] - [LayoutNG] Improve handling of adjoining floats., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 03 May 2018 22:12:07 +0000 - rev 474106
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
c3dd85b106eefeeb83f0c4eb2aacabf66a8247c6: Bug 1457656 [wpt PR 10700] - Parsing tests for CSS UI Level 3, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Thu, 03 May 2018 22:10:50 +0000 - rev 474105
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
c4a237dbf0d9352f51fe047602104b5454f8a686: Bug 1458286 [wpt PR 10737] - Disable kerning in wpt/css/CSS2/floats-clear/floats-143.xht, a=testonly
Koji Ishii <kojii@chromium.org> - Thu, 03 May 2018 22:09:24 +0000 - rev 474104
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
875d698e6ab18a4a140f7d32a15f2c13b187b1c0: Bug 1458290 [wpt PR 10738] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 01 May 2018 20:48:36 +0000 - rev 474103
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1458290 [wpt PR 10738] - Update wpt metadata, a=testonly wpt-pr: 10738 wpt-type: metadata
8e3884bddab52df616088579bf4359e69de92b11: Bug 1458290 [wpt PR 10738] - Move AudioParam tests to WPT, a=testonly
Raymond Toy <rtoy@chromium.org> - Thu, 03 May 2018 22:08:02 +0000 - rev 474102
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
685393774419ff56cc42c4ae1efbb3c17c2ef460: Bug 1458313 [wpt PR 10739] - Revert "Update mozrunner from 7.0.0 to 7.0.1", a=testonly
Geoffrey Sneddon <me@gsnedders.com> - Thu, 03 May 2018 22:06:43 +0000 - rev 474101
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
841d21a6f054e029c991266eea888261c947525a: Bug 1448567 [wpt PR 10166] - Add alternate_hosts, a=testonly
Geoffrey Sneddon <me@gsnedders.com> - Thu, 03 May 2018 22:05:27 +0000 - rev 474100
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
a05f5d59749104dcf28b7a3558e59b2f21dc814f: Bug 1458094 [wpt PR 10721] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 01 May 2018 15:19:23 +0000 - rev 474099
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1458094 [wpt PR 10721] - Update wpt metadata, a=testonly wpt-pr: 10721 wpt-type: metadata
b672b20249e0bcab5d3488980d9f29b6b2b8a613: Bug 1458094 [wpt PR 10721] - Update mozrunner to 7.0.1, a=testonly
pyup-bot <github-bot@pyup.io> - Thu, 03 May 2018 22:04:07 +0000 - rev 474098
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +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
78d5d2a8db2fc555c23e95b03d9bac691399cba8: Bug 1458225 [wpt PR 8805] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 02 May 2018 18:06:14 +0000 - rev 474097
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1458225 [wpt PR 8805] - Update wpt metadata, a=testonly wpt-pr: 8805 wpt-type: metadata
5454546adc0784aca52caf2e73413d9721751e12: Bug 1458225 [wpt PR 8805] - Add references for more CSS Fonts tests, a=testonly
Chris Lilley <chris@w3.org> - Thu, 03 May 2018 22:02:44 +0000 - rev 474096
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1458225 [wpt PR 8805] - Add references for more CSS Fonts tests, a=testonly Automatic update from web-platform-testsMerge pull request #8805 from gsnedders/css-fonts-refs Add references for more CSS Fonts tests -- wpt-commits: ce75e1398b013790125aec23a8c2537aab49ed40 wpt-pr: 8805
036b1f0a38e63dceeae2edb1257b1807eec55aee: Bug 1458116 [wpt PR 10727] - Cookie Store: Move non-ASCII codepoint test cases to dedicated tests, a=testonly
Joshua Bell <jsbell@chromium.org> - Thu, 03 May 2018 22:01:27 +0000 - rev 474095
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1458116 [wpt PR 10727] - Cookie Store: Move non-ASCII codepoint test cases to dedicated tests, a=testonly Automatic update from web-platform-testsCookie Store: Move non-ASCII codepoint test cases to dedicated tests Cookie handling of non-ASCII codepoints is not consistent across browsers, so we definitely want tests that exercise these. To make potential failures here more obvious, make sure that there are dedicated test cases for non-ASCII interop with other ways of getting/setting cookies (HTTP headers, document.cookie). Also, make the document.cookie interop tests symmetric: set/overwrite/delete by CookieStore observed by document.cookie and vice versa. Bug: 729800 Change-Id: I637401e5f8021a2915ba186fbb1cf7a50e940905 Reviewed-on: https://chromium-review.googlesource.com/1036306 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#554936} -- wpt-commits: ea14651f262003177d0ba5819bd2806a1327b12a wpt-pr: 10727
cc6eb4d0a1ee1a6ca486eb622eaa57d68e5270af: Bug 1447888 [wpt PR 10135] - Remove PaymentCurrencyAmount.currencySystem tests, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Thu, 03 May 2018 22:00:04 +0000 - rev 474094
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1447888 [wpt PR 10135] - Remove PaymentCurrencyAmount.currencySystem tests, a=testonly Automatic update from web-platform-testsRemove PaymentCurrencyAmount.currencySystem tests (#10135) -- wpt-commits: eb82c62aeb39dc06b1d1915cd8d30c3f49333a4a wpt-pr: 10135
7cd5006f1365420afb922ced1a1c07feaa27c951: Backout rev 509957c7a9f9 (bug 1456986). r=me a=ryanvm
Ben Kelly <ben@wanderview.com> - Tue, 08 May 2018 07:38:53 -0700 - rev 474093
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Backout rev 509957c7a9f9 (bug 1456986). r=me a=ryanvm
0a1ffd5411da28c2f550620372fe421b4e8e165d: Bug 1420865 - Don't check for CONTENT_MAY_CHANGE_TRANSFORM across layer trees. r=mstange
Ryan Hunt <rhunt@eqrion.net> - Mon, 07 May 2018 16:07:06 -0500 - rev 474092
Push 1757 by ffxbld-merge at Fri, 24 Aug 2018 17:02:43 +0000
Bug 1420865 - Don't check for CONTENT_MAY_CHANGE_TRANSFORM across layer trees. r=mstange MayResample() is used on the content and compositor to determine whether the whole visible region should be or should have been validated. This calculation is done partially by traversing ancestor layers and looking for a flag. This can return different values then in the content side versus the shadow side, which in this case leads to artifacts. This commit tries to solve the problem by ignoring layers that content is unaware of. This works, but has the downside that resampling artifacts could show up if the parent process is truly doing animations that require resampling. MozReview-Commit-ID: 4TW6nzxS6E
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip