0758372d44f22bfb7727000355580db2bd578a47: Bug 1512017 [wpt PR 14356] - [wptrunner] Support any Sauce Connect argument, a=testonly
jugglinmike <mike@mikepennisi.com> - Thu, 13 Dec 2018 13:57:55 +0000 - rev 450682
Bug 1512017 [wpt PR 14356] - [wptrunner] Support any Sauce Connect argument, a=testonly Automatic update from web-platform-tests [wptrunner] Support any Sauce Connect argument (#14356) Implement the command-line argument `--sauce-connect-arg` as a pass-through to the Sauce Connect binary. This gives users more control over the way the binary is configured which is particularly important in combination with the existing `--sauce-connect-binary` argument (since the list of available arguments is subject to change between releases). -- wpt-commits: 3f5d8afff4ee3b156d34d1329fb887f93d927316 wpt-pr: 14356
d9ee83aed3acbed374f1078aa5ba3667ee983f4f: Bug 1512158 [wpt PR 14375] - Sync Mozilla CSS tests as of 2018-12-05, a=testonly
L. David Baron <dbaron@dbaron.org> - Thu, 13 Dec 2018 13:57:49 +0000 - rev 450681
Bug 1512158 [wpt PR 14375] - Sync Mozilla CSS tests as of 2018-12-05, a=testonly Automatic update from web-platform-tests Sync Mozilla CSS tests as of https://hg.mozilla.org/mozilla-central/rev/caae48e4e6cf4477e11b6464bccdd5ba679ae31a . (#14375) This contains changes from [bug 1511963](https://bugzilla.mozilla.org/show_bug.cgi?id=1511963) by @mrego, reviewed by @emilio. -- wpt-commits: 54e379bd1da6e2f09e258c7bdef4b8e289dc546e wpt-pr: 14375
e4b879730a2a13695d845d3b1d8b55c091f4d869: Bug 1489123 [wpt PR 12872] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 05 Dec 2018 13:03:00 +0000 - rev 450680
Bug 1489123 [wpt PR 12872] - Update wpt metadata, a=testonly wpt-pr: 12872 wpt-type: metadata
4b6edf8b08ba2ccc88eb5b7c22a106c440514bbe: Bug 1489123 [wpt PR 12872] - [Trusted Types] Tests from WICG GitHub ported to WPT, a=testonly
Daniel Vogelheim <vogelheim@chromium.org> - Thu, 13 Dec 2018 13:57:44 +0000 - rev 450679
Bug 1489123 [wpt PR 12872] - [Trusted Types] Tests from WICG GitHub ported to WPT, a=testonly Automatic update from web-platform-tests [Trusted Types] Tests from WICG GitHub ported to WPT WICG GitHub = https://github.com/WICG/trusted-types/tree/master/tests ported Bug: 739170 Change-Id: I56563c16facd7c17d79e7b5625115a0f045618f8 Reviewed-on: https://chromium-review.googlesource.com/c/1209708 Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613937} -- wpt-commits: 290b849c576ec3f2c13a78d05b2210b3655f4964 wpt-pr: 12872
fbfedc05d1dd5cb63ba01611ad989abe052cd115: Bug 1512131 [wpt PR 14372] - Update interfaces/webxr.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 13 Dec 2018 13:57:37 +0000 - rev 450678
Bug 1512131 [wpt PR 14372] - Update interfaces/webxr.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webxr.idl (#14372) Source: https://github.com/tidoust/reffy-reports/blob/81fd807/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463710129 -- wpt-commits: 9f57a56b6b8326a066fb720df41cbc283c8ebc44 wpt-pr: 14372
b42297cc59f967be0fd0abe8303b8b3182389966: Bug 1512130 [wpt PR 14371] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 05 Dec 2018 08:42:37 +0000 - rev 450677
Bug 1512130 [wpt PR 14371] - Update wpt metadata, a=testonly wpt-pr: 14371 wpt-type: metadata
34b92cef3552f78a2d8ddc2cb85e26f47c87c8f5: Bug 1512130 [wpt PR 14371] - Update interfaces/web-nfc.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 13 Dec 2018 13:57:32 +0000 - rev 450676
Bug 1512130 [wpt PR 14371] - Update interfaces/web-nfc.idl, a=testonly Automatic update from web-platform-tests Update interfaces/web-nfc.idl (#14371) Source: https://github.com/tidoust/reffy-reports/blob/81fd807/whatwg/idl/web-nfc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463710129 -- wpt-commits: e298bbf529549e8e3d4380af2a26851453e4c3dc wpt-pr: 14371
9d7bbdbb5355477b3856f197a0cf7f1a83a9bbe2: Bug 1511484 [wpt PR 14311] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 01 Dec 2018 09:09:36 +0000 - rev 450675
Bug 1511484 [wpt PR 14311] - Update wpt metadata, a=testonly wpt-pr: 14311 wpt-type: metadata
d8062a5a3bd5d2d9cc2e0d49865646652a627a7d: Bug 1511484 [wpt PR 14311] - Don't estimate the top of bottom-aligned OOFs as bottom., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 13 Dec 2018 13:57:27 +0000 - rev 450674
Bug 1511484 [wpt PR 14311] - Don't estimate the top of bottom-aligned OOFs as bottom., a=testonly Automatic update from web-platform-tests Don't estimate the top of bottom-aligned OOFs as bottom. We'll incorrectly think that we get fragmented in that case, which will lead to incorrect height, which will lead to incorrect top offset, which will lead to incorrect fragmentation. This has probably been the cause for a flaky web test, that behaved even worse in LayoutNG, because in NG we force legacy layout as soon as fragmentation is involved (so when entering printing, we typically need to rebuild the entire layout object tree, with no former height to base the bottom estimate on (which is what saved us when NG is disabled - ehm, at least most of the time)). Bug: 910300 Change-Id: I8e152f77e9a94bb05e51f02a24be6ef5fe03c6f9 Cq-Include-Trybots: luci.chromium.try​:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1355920 Reviewed-by: Aleks Totic <atotic@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#613930} -- wpt-commits: 66004f50a8ef54560dc61294ee1cd61cbb866b20 wpt-pr: 14311
0f33ddfa45f60ff2297d79aa14910442511bb272: Bug 1504357 [wpt PR 14303] - [Gecko Bug 1504357] Make sure --repeat-until-unexpected doesn't loop over zero tests, a=testonly
Wes Kocher <wkocher@mozilla.com> - Thu, 13 Dec 2018 13:57:25 +0000 - rev 450673
Bug 1504357 [wpt PR 14303] - [Gecko Bug 1504357] Make sure --repeat-until-unexpected doesn't loop over zero tests, a=testonly Automatic update from web-platform-tests Make sure --repeat-until-unexpected doesn't loop over zero tests If zero tests are selected to run while --repeat-until-unexpected is specified, wptrunner can get into a fast infinite loop of running nothing until killed by the user. This patch should stop that from happening by breaking the loop after the first iteration of nothing finishes. Differential Revision: https://phabricator.services.mozilla.com/D13204 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1504357 gecko-commit: f988af9437f591cc5c7d3917ba370e2edc82d1a6 gecko-integration-branch: central gecko-reviewers: jgraham -- Update wptrunner.py -- wpt-commits: ff755aa4b71299ecd172948a40f21c6ee0150371, f4449f82694932024c55f7e38b3328595f5c3aba wpt-pr: 14303
b658e04623b571a27ff5faa0c435a406eae74c13: Bug 1511975 [wpt PR 14352] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 04 Dec 2018 14:58:53 +0000 - rev 450672
Bug 1511975 [wpt PR 14352] - Update wpt metadata, a=testonly wpt-pr: 14352 wpt-type: metadata
1944a91a94e03f96d6687d527bb7620d8e1b171a: Bug 1511975 [wpt PR 14352] - [LayoutNG] Honor {min,max}-inline-size when using cached intrinsic size., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 13 Dec 2018 13:57:21 +0000 - rev 450671
Bug 1511975 [wpt PR 14352] - [LayoutNG] Honor {min,max}-inline-size when using cached intrinsic size., a=testonly Automatic update from web-platform-tests [LayoutNG] Honor {min,max}-inline-size when using cached intrinsic size. We store cached min/max intrinsic inline sizes in legacy layout objects. These are normally constrained against {min,max}-inline-size, but not if those values are percentage based, since percentages are obviously not resolvable at the time of calculating intrinsic sizes. In such cases we cannot use the cached values directly. Calculate intrinsic size and apply constraints on our own in such cases. Bug: 900390 Change-Id: I90b8ab590fa97e8ec7929bc1af38cf3824f9ea6b Reviewed-on: https://chromium-review.googlesource.com/c/1360853 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#613889} -- wpt-commits: 30b3f1de6e092e38e07a969eb5d390d3d95b66f8 wpt-pr: 14352
53ed7067dd26d69a5dd38d1a7cebe7f97a2c625f: Bug 1512119 [wpt PR 14368] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 05 Dec 2018 04:59:27 +0000 - rev 450670
Bug 1512119 [wpt PR 14368] - Update wpt metadata, a=testonly wpt-pr: 14368 wpt-type: metadata
5995dacf9251b00590e9104759258b139f3edc00: Bug 1512119 [wpt PR 14368] - [css-text] line-height fix on overflow-wrap-break-word-004 and -005, a=testonly
MurakamiShinyu <murakami@vivliostyle.org> - Thu, 13 Dec 2018 13:57:16 +0000 - rev 450669
Bug 1512119 [wpt PR 14368] - [css-text] line-height fix on overflow-wrap-break-word-004 and -005, a=testonly Automatic update from web-platform-tests [css-text] line-height fix on overflow-wrap-break-word-004 and -005 tests - `line-height: 1em` was specified on the `.test {...}` but not on the `.red` and `.fail` blocks. As a result, the line-height of the `.red` and `.fail` blocks depended on the browser, and the red color appeared on Firefox. -- Merge pull request #14368 from MurakamiShinyu/overflow-wrap [css-text] line-height fix on overflow-wrap-break-word-004 and -005 -- wpt-commits: 9ccd954c04795e3db33da504e9d647d0eefe5d92, aaa8f8269f650d6c0e775345c29e5774c5f41d2b wpt-pr: 14368
54698426b658b7a32579fe8fcbd7699601c0c91f: Bug 1505992 [wpt PR 13990] - Refactor storage estimate wpt to use async/await., a=testonly
Jarryd <jarrydg@chromium.org> - Thu, 13 Dec 2018 13:57:13 +0000 - rev 450668
Bug 1505992 [wpt PR 13990] - Refactor storage estimate wpt to use async/await., a=testonly Automatic update from web-platform-tests Refactor storage estimate wpt to use async/await. Change-Id: Iec6ddc03ce5a813f219273e4a8a7d5098b3fb936 Reviewed-on: https://chromium-review.googlesource.com/c/1318739 Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#613817} -- wpt-commits: c4eb7b76e3ed08aea6466776064581d2d9276d1f wpt-pr: 13990
ba7287e6a1fc4536950eeb1b0f9b479060484956: Bug 1512111 [wpt PR 14365] - testharness.md: Remove errant spaces in file paths, a=testonly
Kai Ninomiya <kainino@chromium.org> - Thu, 13 Dec 2018 13:57:11 +0000 - rev 450667
Bug 1512111 [wpt PR 14365] - testharness.md: Remove errant spaces in file paths, a=testonly Automatic update from web-platform-tests testharness.md: Remove errant spaces in file paths Removes spaces in /common /subset-tests.js /common/subset-tests-by- key.js -- wpt-commits: c05265a2860ab153b67362b9aa4d1452c401114f wpt-pr: 14365
237c20fa70ed357722958e47fa0624ebe4141705: Bug 1511777 [wpt PR 14334] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Dec 2018 08:11:53 +0000 - rev 450666
Bug 1511777 [wpt PR 14334] - Update wpt metadata, a=testonly wpt-pr: 14334 wpt-type: metadata
f9035753ebcf2e315887e6044ea132071b6ef634: Bug 1511777 [wpt PR 14334] - [css-text] Update 'line-break' tests, a=testonly
MurakamiShinyu <murakami@vivliostyle.org> - Thu, 13 Dec 2018 13:57:07 +0000 - rev 450665
Bug 1511777 [wpt PR 14334] - [css-text] Update 'line-break' tests, a=testonly Automatic update from web-platform-tests [css-text] Update 'line-break' tests ### Fix test file name numbering The problem was that `line-break-normal-*` and `line-break-strict-*` had diffrent numbering for same ranges, e.g. `line-break-normal-021` and `line-break-strict-014` for same iteration marks. It was confusing, so I changed the numbering for 'normal' to be the same as for 'strict'. - line-break-normal-021 → line-break-normal-014 - line-break-normal-022 → line-break-normal-015 - line-break-normal-023a → line-break-normal-016a - line-break-normal-023b → line-break-normal-016b - line-break-normal-024a → line-break-normal-017a - line-break-normal-024b → line-break-normal-017b ### Fix tests for Inseparatable characters The tests for Inseparatable characters `line-break-strict-015` and `line-break-normal-015` (was `line-break-normal-022`) had wrong assertion "does not allow line breaking **before** inseparable characters". This should be "does not allow line breaking **between** inseparable characters". I changed the tests to test line breaking **between** (not **before**) two inseparable characters. ### Fix tests for Centered punctuation marks The tests for Centered punctuation marks `line-break-strict-016a` and `line-break-normal-016a` (was `line-break-normal-023a`) contained tests for EAW=Narrow characters (U+003A, U+003B, U+0021, U+003F) that are excluded in the current 'line-break' spec. ### Fix tests for Postfixes The tests for Postfixes `line-break-strict-017a` and `line-break-normal-017a` (was `line-break-normal-024a`) contained tests for EAW=Narrow characters (U+0025 and U+00A2) that are excluded in the current 'line-break' spec. ### Add tests for Prefixes Added the tests for line breaking after Prefixes `line-break-*-018`. ### Add 'loose' and 'normal' values tests that were missing - line-break-loose-011 .. line-break-loose-017b - line-break-normal-011 .. line-break-normal-013 ### Adjust width of the test block I changed the width of the test block `p.test, p.control {...}` that was `width: 10em` to `width: 10.2em`. This extra (.2em) width is needed to prevent unexpected line breaking caused by some symbol characters wider than 1em. I found this problem with `line-break-loose-018`. The width of U+2116 "№" is slightly wider than 1em and if the block width is 10em the line breaking occurs before that character, and the test always fails. -- wpt-commits: 614fd870e47c9f4e76291e5af4e32b676c0acac0 wpt-pr: 14334
9a23ac22789e0c1e5ae5e214cacc672d2c1a03b9: Bug 1512000 [wpt PR 14353] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 04 Dec 2018 17:22:32 +0000 - rev 450664
Bug 1512000 [wpt PR 14353] - Update wpt metadata, a=testonly wpt-pr: 14353 wpt-type: metadata
24a67626fd7f78b0758ea56be40288e70b4bab60: Bug 1512000 [wpt PR 14353] - [css-text] Some fixes on 'word-break-break-all-*' tests, a=testonly
MurakamiShinyu <murakami@vivliostyle.org> - Thu, 13 Dec 2018 13:57:02 +0000 - rev 450663
Bug 1512000 [wpt PR 14353] - [css-text] Some fixes on 'word-break-break-all-*' tests, a=testonly Automatic update from web-platform-tests [css-text] Some fixes on 'word-break-break-all-*' tests ### word-break-break-all-010 and word-break-break-all-011 - `line-height: 1em` was specified on the `.test {...}` but not on the `.red {...}`. As a result, the line-height of the `.red` block depended on the browser, and the red color appeared on Firefox. ### word-break-break-all-020 Fix erros (typo?) - `div::nth-of-type` → `div:nth-of-type` - `break-word` → `break-all` -- wpt-commits: 3960fff73862bd9745f8b0add9358e923f916dcb wpt-pr: 14353
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip