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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
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
acaeb9ce550b878669219a0885d456132575094a: Bug 1511876 [wpt PR 14346] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Dec 2018 22:34:36 +0000 - rev 450662
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1511876 [wpt PR 14346] - Update wpt metadata, a=testonly wpt-pr: 14346 wpt-type: metadata
15bf13b385f67f164c21736ec31b4c833645a668: Bug 1511876 [wpt PR 14346] - [ScrollTimeline] Begin upstreaming tests to WPT, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Thu, 13 Dec 2018 13:56:57 +0000 - rev 450661
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1511876 [wpt PR 14346] - [ScrollTimeline] Begin upstreaming tests to WPT, a=testonly Automatic update from web-platform-tests [ScrollTimeline] Begin upstreaming tests to WPT This CL uploads some basic construction tests for ScrollTimeline. Since the Chrome implementation still requires timeRange, it is left in for now (but documented!). Spec: https://wicg.github.io/scroll-animations Bug: 911254 Change-Id: Ia7da845eddcd27ea6e7d3fbaf3a008cbdf6d149a Reviewed-on: https://chromium-review.googlesource.com/c/1354222 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#613666} -- wpt-commits: 164bf82fe832a15740af1b0445e6c59841a0536a wpt-pr: 14346
1d7856790c3bf597d864472cd8a8cbec0d0410ae: Bug 1477182 [wpt PR 12086] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 19 Sep 2018 16:08:02 +0000 - rev 450660
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1477182 [wpt PR 12086] - Update wpt metadata, a=testonly wpt-pr: 12086 wpt-type: metadata
c72a48e0c5db12308cddb0a01d48418821c09c3d: Bug 1477182 [wpt PR 12086] - WorkerGlobalScope::importScripts() modified to accept TrustedTypes, a=testonly
Daniel Vogelheim <vogelheim@chromium.org> - Thu, 13 Dec 2018 13:56:52 +0000 - rev 450659
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1477182 [wpt PR 12086] - WorkerGlobalScope::importScripts() modified to accept TrustedTypes, a=testonly Automatic update from web-platform-tests WorkerGlobalScope::importScripts() modified to accept TrustedTypes Existing implementation made private and renamed importScriptsFromString. New version wraps importScriptsFromString. Service_Worker_Global_Scope::importScripts() signature adjusted to accept TrustedTypes. Bug: 739170 Change-Id: Ifa7d9e9f13f0903ecdf0b4c1553f6039141b9b76 Reviewed-on: https://chromium-review.googlesource.com/c/1144825 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#613538} -- wpt-commits: 1f9bc10d3a98e685e5cd7671d5ae40a5ff8828d6 wpt-pr: 12086
2176b9c189d3bd7fdc81739158a6c9adef2f94ce: Bug 1510784 [wpt PR 14280] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Nov 2018 21:26:29 +0000 - rev 450658
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1510784 [wpt PR 14280] - Update wpt metadata, a=testonly wpt-pr: 14280 wpt-type: metadata
5350bb6eb84c067e86637a34bc84fcab8936a536: Bug 1510784 [wpt PR 14280] - Rework of "inherit the navigation initiator when navigating", a=testonly
Andy Paicu <andypaicu@chromium.org> - Thu, 13 Dec 2018 13:56:48 +0000 - rev 450657
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1510784 [wpt PR 14280] - Rework of "inherit the navigation initiator when navigating", a=testonly Automatic update from web-platform-tests Rework of "inherit the navigation initiator when navigating" Spec: https://w3c.github.io/webappsec-csp/#initialize-document-csp This is a rework and reland of https://chromium-review.googlesource.com/c/chromium/src/+/1314633 The initial patch got reverted because it did not pass the trusty leak build checks. The issue was that holding to the initiator document as a member in FrameLoader was holding said document alive unreasonably long. Instead this rework holds a copy of the initiator's CSP. Bug: 905301, 894228, 836148 Change-Id: Ic12c28d20c53def5d6753449c3c4da7de5242ca2 Reviewed-on: https://chromium-review.googlesource.com/c/1353978 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#613521} -- wpt-commits: 4a0a94b4bd94bfb61eb7e5100601f1461b39ccc7 wpt-pr: 14280
419c15985bb50c17e74fd0561f2c806b8e426338: Bug 1511832 [wpt PR 14339] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Dec 2018 16:03:04 +0000 - rev 450656
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1511832 [wpt PR 14339] - Update wpt metadata, a=testonly wpt-pr: 14339 wpt-type: metadata
21a2dfe5abc11945e7aed8c0bfe9bdf042fce6a5: Bug 1511832 [wpt PR 14339] - Fixes to the plugin-types csp checks and added empty directive check, a=testonly
Andy Paicu <andypaicu@chromium.org> - Thu, 13 Dec 2018 13:56:43 +0000 - rev 450655
Push 35208 by csabou@mozilla.com at Sat, 15 Dec 2018 02:48:07 +0000
Bug 1511832 [wpt PR 14339] - Fixes to the plugin-types csp checks and added empty directive check, a=testonly Automatic update from web-platform-tests Fixes to the plugin-types csp checks and added empty directive check Fixed the external/wpt/content-security-policyplugin-types tests as the current ones are actually entirely useless as they pretty much always pass. Discovered and raised crbug.com/911114, also skipping the (now correct) tests that uncovered this issue. Added new test for empty plugin-types directive blocking every plugin. Removed tests in http/tests/security/contentSecurityPolicy that are direct 1-to-1 equivalents of these tests. Spec: https://github.com/w3c/webappsec-csp/pull/374 Bug: 694525 Change-Id: I91a548c6035a82310be077501934a51cf85525a2 Reviewed-on: https://chromium-review.googlesource.com/c/1358457 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613517} -- wpt-commits: 0b2da26c5d50f3b6fe2976f21535c6fc3ef78a08 wpt-pr: 14339
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip