47729ad34d0c910d0f3a878876cb96f582b4bd57: Bug 1448791 [wpt PR 10174] - Keep track of all pending slot assignments, and recalc all before UpdateStyle phase, a=testonly
Hayato Ito <hayato@chromium.org> - Mon, 09 Apr 2018 18:20:53 +0000 - rev 413669
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448791 [wpt PR 10174] - Keep track of all pending slot assignments, and recalc all before UpdateStyle phase, a=testonly Automatic update from web-platform-testsKeep track of all pending slot assignments, and recalc all before UpdateStyle phase For the purpose of rendering, Blink must calculate all pending slot assignments before UpdateStyle phase. Unless that, a recursive RecalcStyle() may not traverse a node which should be re-attached. e.g. Suppose the following tree, where #d1 is assigned to a slot. host ├──/shadow-root │ └── slot name=s1 └── div id=d1 slot=s1 Then, we change #d1's slot attribute to s2, like: > document.querySelector('#d1').setAttribute('slot', 's2'); host ├──/shadow-root │ └── slot name=s1 └── div id=d1 slot=s2 In this case, #d1 should be removed from a LayoutTree. In other words, Blink has to reattach #d1 somehow. However, if we don't recalc a slot assignment for the shadow tree before UpdateStyle, a recursive RecalcStyle never traverses the sub-tree because child-needs-style-recalc flag is not set for the node (and its ancestor nodes). A flag should be set as a result of slot assignment recalc. Thanks to the Incremental Shadow DOM, a slot assignemt recalc now becomes a local operatoin on each shadow tree, rather than one global operation for every shadow trees. We don't need to traverse a composed tree to recalc all. We can recalc a slot assignment for each shadow tree directly, without traversing a composed tree. For a shadow tree which is not connected, we don't need to recalc its slot assignment before UpdateStyle because such a shadow tree shouldn't have any effect on rendering. Lazy slot assignment recalc is enough for such a shadow tree. This CL doesn't introduce any optimization to minimize the number of to-be-reattached nodes. I'll optimize that as a next task. I'll use a sort of dynamic programming there, as I did at https://chromium-review.googlesource.com/c/chromium/src/+/535493 for non-Incremental Shadow DOM. Except for the performance, this CL should be the last part of Incremental Shadow DOM from the external behavior's perspective. Style and Layout should work correctly after this CL, even with Incremental Shadow DOM. BUG=776656 Change-Id: Id18e87ff59d92863c68c571e7db09253c08aa91f Reviewed-on: https://chromium-review.googlesource.com/964062 Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#546458} wpt-commits: 1d25beb750906894ae1306c69ba2290e527b7048 wpt-pr: 10174 wpt-commits: 1d25beb750906894ae1306c69ba2290e527b7048 wpt-pr: 10174
620e06af2cc635316118d703303f61df7d848505: Bug 1448643 [wpt PR 10169] - expand tests to test in reverse direction, a=testonly
Kriti Singh <kritisingh1.ks@gmail.com> - Mon, 09 Apr 2018 18:20:25 +0000 - rev 413668
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448643 [wpt PR 10169] - expand tests to test in reverse direction, a=testonly Automatic update from web-platform-testsTest that event handlers set on the window object are found on the body element (#10169) Based on event-handler-attributes-body-window.html. wpt-commits: 6fca0b2cd6f7f8d915e78b1e3aa00a3ac6893019 wpt-pr: 10169 wpt-commits: 6fca0b2cd6f7f8d915e78b1e3aa00a3ac6893019 wpt-pr: 10169
b40e9634c84b53bb1e03ad0da9ee009bd790c800: Bug 1449445 [wpt PR 10207] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Mar 2018 07:27:29 +0000 - rev 413667
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449445 [wpt PR 10207] - Update wpt metadata, a=testonly wpt-pr: 10207 wpt-type: metadata
a405c706011b8e6a41aac0168102314473bd1b38: Bug 1449445 [wpt PR 10207] - [css-typed-om] support x, y, cx, cy properties, a=testonly
Hwanseung Lee <hs1217.lee@samsung.com> - Mon, 09 Apr 2018 18:19:49 +0000 - rev 413666
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449445 [wpt PR 10207] - [css-typed-om] support x, y, cx, cy properties, a=testonly Automatic update from web-platform-tests[css-typed-om] support x, y, cx, cy properties x[1], y[2], cx[3], cy[4] are added to support in whitelist. and test file are also added. [1]https://svgwg.org/svg2-draft/geometry.html#X [2]https://svgwg.org/svg2-draft/geometry.html#Y [3]https://svgwg.org/svg2-draft/geometry.html#CX [4]https://svgwg.org/svg2-draft/geometry.html#CY Bug: 820299 Change-Id: I46ced4427a5e7b2e08aa132fc0b8c5d2e1f19d22 Reviewed-on: https://chromium-review.googlesource.com/983077 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#546426} wpt-commits: 3db7bb79512c7962760cd42a32c01aaeb9f68860 wpt-pr: 10207 wpt-commits: 3db7bb79512c7962760cd42a32c01aaeb9f68860 wpt-pr: 10207
0d24098f0a4f928139af552c34229ebec8af4997: Bug 1449129 [wpt PR 10193] - Re-land: "Don't adjust the NavigationTimings on redirects", a=testonly
Kinuko Yasuda <kinuko@chromium.org> - Mon, 09 Apr 2018 18:19:21 +0000 - rev 413665
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449129 [wpt PR 10193] - Re-land: "Don't adjust the NavigationTimings on redirects", a=testonly Automatic update from web-platform-testsRe-land: "Don't adjust the NavigationTimings on redirects" The reason for revert was the new navigation timing test expectations (that got commited right before the original change) had a FAIL expectation for the particular event order that this change was fixing. Original change's description: > Don't adjust the NavigationTimings on redirects > > We adjust the timings in WebDocumentLoaderImpl::UpdateNavigation(), > shouldn't update in each AddRedirect() (which is called in a batch > way after all the redirects are handled in the browser process with PlzNavigate, > adjusting timings there with current timestamp is totally wrong) > > R=​ksakamoto,arthursonzogni > > Bug: 813889 > Change-Id: I3a57d3fdf1833c300feb5ee61737b64cece0946b > Reviewed-on: https://chromium-review.googlesource.com/974673 > Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> > Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#546001} Bug: 813889 Change-Id: I6f5c0ba1196fa1dd52225036820b29a95569ac21 Reviewed-on: https://chromium-review.googlesource.com/981913 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#546365} wpt-commits: 383fd735a55bd21daef6a07430d8f6ce3852f30b wpt-pr: 10193 wpt-commits: 383fd735a55bd21daef6a07430d8f6ce3852f30b wpt-pr: 10193
54d89678fcd71638f020c62307571e14821bbdde: Bug 1449085 [wpt PR 10189] - [css-typed-om] Support some text-decoration properties., a=testonly
Darren Shen <shend@chromium.org> - Mon, 09 Apr 2018 18:18:53 +0000 - rev 413664
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449085 [wpt PR 10189] - [css-typed-om] Support some text-decoration properties., a=testonly Automatic update from web-platform-tests[css-typed-om] Support some text-decoration properties. Adds tests for: - text-decoration - text-decoration-line - text-decoration-skip (not implemented in Blink) - text-decoration-skip-ink - text-decoration-width (not implemented in Blink) text-decoration-line uses a weird internal structure for CSSValues, so we have to encode/decode to that structure when getting/setting. Failing tests because for some reason we ignore 'blink' for the computed value. Blink also doesn't support 'spelling-error' and 'grammar-error' yet. Bug: 820299 Change-Id: I60e8c3958c9b3a784177c9813a7325aa26e39581 Reviewed-on: https://chromium-review.googlesource.com/981717 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#546364} wpt-commits: 62d701058e3ddedb88df00fadb4e05802b7e8cbc wpt-pr: 10189 wpt-commits: 62d701058e3ddedb88df00fadb4e05802b7e8cbc wpt-pr: 10189
82ec32afc87e49787a48655ee0c8fc0d76f87293: Bug 1449176 [wpt PR 10196] - [css-typed-om] support r and rx and ry properties, a=testonly
Hwanseung Lee <hs1217.lee@samsung.com> - Mon, 09 Apr 2018 18:18:25 +0000 - rev 413663
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449176 [wpt PR 10196] - [css-typed-om] support r and rx and ry properties, a=testonly Automatic update from web-platform-tests[css-typed-om] support r and rx and ry properties r[1], rx[2], ry[3] are added to support in whitelist. and test file are also added. [1]https://svgwg.org/svg2-draft/geometry.html#R [2]https://svgwg.org/svg2-draft/geometry.html#RX [3]https://svgwg.org/svg2-draft/geometry.html#RY Bug: 820299 Change-Id: I51457648ca07aaf06cf15bd28452d5ad8099d2e3 Reviewed-on: https://chromium-review.googlesource.com/981918 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#546302} wpt-commits: 45d92ebc552d67936169a17e86980636b112bf18 wpt-pr: 10196 wpt-commits: 45d92ebc552d67936169a17e86980636b112bf18 wpt-pr: 10196
a006df0d2383f73319a8fe538bb347218e7779ca: Bug 1447894 [wpt PR 10136] - Worker: Add tests for import.meta.url on DedicatedWorker, a=testonly
Hiroki Nakagawa <nhiroki@chromium.org> - Mon, 09 Apr 2018 18:17:57 +0000 - rev 413662
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1447894 [wpt PR 10136] - Worker: Add tests for import.meta.url on DedicatedWorker, a=testonly Automatic update from web-platform-testsWorker: Add tests for import.meta.url on DedicatedWorker Bug: 680046 Change-Id: Ieb341c5922ad247961ca477893037896dbd88ea6 Reviewed-on: https://chromium-review.googlesource.com/974726 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#546254} wpt-commits: 8ccaab2a5566e719948722108fa04404e3a43849 wpt-pr: 10136 wpt-commits: 8ccaab2a5566e719948722108fa04404e3a43849 wpt-pr: 10136
9d793d1842c80a75ec259433056a7e71f88141ee: Bug 1448969 [wpt PR 10182] - Port nested sticky tests from reftests to JS tests, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Mon, 09 Apr 2018 18:17:27 +0000 - rev 413661
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448969 [wpt PR 10182] - Port nested sticky tests from reftests to JS tests, a=testonly Automatic update from web-platform-testsPort nested sticky tests from reftests to JS tests Bug: 699244 Change-Id: Ia85a44be9d9f7b0d0db382892520f2755523f514 Reviewed-on: https://chromium-review.googlesource.com/980236 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#546172} wpt-commits: 8214a83ae15810425ebbdb305ba5a0a746f4b36e wpt-pr: 10182 wpt-commits: 8214a83ae15810425ebbdb305ba5a0a746f4b36e wpt-pr: 10182
e838f9fbb674f0980f2590f93ad85575b6ec1fd4: Bug 1448953 [wpt PR 10180] - Replace 'enabledMethods' array with 'method' string., a=testonly
Rouslan Solomakhin <rouslan@google.com> - Mon, 09 Apr 2018 18:16:59 +0000 - rev 413660
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448953 [wpt PR 10180] - Replace 'enabledMethods' array with 'method' string., a=testonly Automatic update from web-platform-testsMerge pull request #10180 from rsolomakhin/method Replace 'enabledMethods' array with 'method' string. wpt-commits: e96e038f14133dd891af50571dfeeda1210e8f36 wpt-pr: 10180 wpt-commits: e96e038f14133dd891af50571dfeeda1210e8f36 wpt-pr: 10180
b00b203a7eea797717096c9c94b3256038e17217: Bug 1448393 [wpt PR 10158] - [css-typed-om] Add support for the column-width property., a=testonly
Rune Lillesveen <futhark@chromium.org> - Mon, 09 Apr 2018 18:16:31 +0000 - rev 413659
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448393 [wpt PR 10158] - [css-typed-om] Add support for the column-width property., a=testonly Automatic update from web-platform-tests[css-typed-om] Add support for the column-width property. Bug: 820299 Change-Id: I9e380416b18f30294fe7cb969a0ce7d0ab1fd7bd Reviewed-on: https://chromium-review.googlesource.com/977910 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#546082} wpt-commits: 6135f17c8825701fc2ec62117a08fdcadca4a0a2 wpt-pr: 10158 wpt-commits: 6135f17c8825701fc2ec62117a08fdcadca4a0a2 wpt-pr: 10158
3325454495c2e6d7233acc99fccf9a1a0ab219da: Bug 1449101 [wpt PR 10190] - Revert "Don't adjust the NavigationTimings on redirects", a=testonly
Ben Wells <benwells@chromium.org> - Mon, 09 Apr 2018 18:16:03 +0000 - rev 413658
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449101 [wpt PR 10190] - Revert "Don't adjust the NavigationTimings on redirects", a=testonly Automatic update from web-platform-testsRevert "Don't adjust the NavigationTimings on redirects" This reverts commit aeecb4f32ece14a8a294e4f9b80a5bb2278091c9. Reason for revert: Causing lots of failures on webkit bots, e.g.: https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty/42143 Original change's description: > Don't adjust the NavigationTimings on redirects > > We adjust the timings in WebDocumentLoaderImpl::UpdateNavigation(), > shouldn't update in each AddRedirect() (which is called in a batch > way after all the redirects are handled in the browser process with PlzNavigate, > adjusting timings there with current timestamp is totally wrong) > > R=​ksakamoto,arthursonzogni > > Bug: 813889 > Change-Id: I3a57d3fdf1833c300feb5ee61737b64cece0946b > Reviewed-on: https://chromium-review.googlesource.com/974673 > Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> > Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#546001} TBR=kinuko@chromium.org,ksakamoto@chromium.org,arthursonzogni@chromium.org Change-Id: I467ed888084ea0eda06faa903d1797fabffc47da No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 813889 Reviewed-on: https://chromium-review.googlesource.com/981912 Reviewed-by: Ben Wells <benwells@chromium.org> Commit-Queue: Ben Wells <benwells@chromium.org> Cr-Commit-Position: refs/heads/master@{#546025} wpt-commits: 2e480369d06977c6afeda0d45bd67f0644b787b4 wpt-pr: 10190 wpt-commits: 2e480369d06977c6afeda0d45bd67f0644b787b4 wpt-pr: 10190
a9a6d7d5e674c7010a1a58e68961cee651a57f27: Bug 1448441 [wpt PR 10161] - [css-layout-api] Allow developers to position fragments., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Mon, 09 Apr 2018 18:15:34 +0000 - rev 413657
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448441 [wpt PR 10161] - [css-layout-api] Allow developers to position fragments., a=testonly Automatic update from web-platform-tests[css-layout-api] Allow developers to position fragments. This implements the LayoutFragment.inlineOffset and LayoutFragment.blockOffset attributes. The tests added simply re-create the reference by setting these two attributes in different text directions and writing modes. Change-Id: I1865403ca12e3b174738ee93320eae5ba16ac292 Bug: 726125 Reviewed-on: https://chromium-review.googlesource.com/971832 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#546018} wpt-commits: 8ec345bcd24282ce94960fc0b11ca057bec393be wpt-pr: 10161 wpt-commits: 8ec345bcd24282ce94960fc0b11ca057bec393be wpt-pr: 10161
c114530770d67bef7f077c0102ec8627b203c250: Bug 1448224 [wpt PR 10150] - Don't adjust the NavigationTimings on redirects, a=testonly
Kinuko Yasuda <kinuko@chromium.org> - Mon, 09 Apr 2018 18:15:05 +0000 - rev 413656
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448224 [wpt PR 10150] - Don't adjust the NavigationTimings on redirects, a=testonly Automatic update from web-platform-testsDon't adjust the NavigationTimings on redirects We adjust the timings in WebDocumentLoaderImpl::UpdateNavigation(), shouldn't update in each AddRedirect() (which is called in a batch way after all the redirects are handled in the browser process with PlzNavigate, adjusting timings there with current timestamp is totally wrong) R=ksakamoto,arthursonzogni Bug: 813889 Change-Id: I3a57d3fdf1833c300feb5ee61737b64cece0946b Reviewed-on: https://chromium-review.googlesource.com/974673 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#546001} wpt-commits: c32afde8ec7f0e10b5b5f27c4907095c37303e71 wpt-pr: 10150 wpt-commits: c32afde8ec7f0e10b5b5f27c4907095c37303e71 wpt-pr: 10150
2727b165f16ccc4ee1830e9eb76af9da0daf1fe4: Bug 1448758 [wpt PR 10173] - service_worker: Add tests for navigation timing, a=testonly
Kenichi Ishibashi <bashi@chromium.org> - Mon, 09 Apr 2018 18:14:37 +0000 - rev 413655
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448758 [wpt PR 10173] - service_worker: Add tests for navigation timing, a=testonly Automatic update from web-platform-testsservice_worker: Add tests for navigation timing This CL adds some tests for PerformanceNavigationTiming which are involved with service worker. - SW intercepts a navigation - SW falls back to network - Redirect and SW intercepts a navigation These tests check `workerStart <= fetchStart` because starting a worker should happen before fetching a resource when service worker is involved. Bug: 782958 Change-Id: Idd3fa8f76a328e77ee531b81bd91ee3db223f12c Reviewed-on: https://chromium-review.googlesource.com/979873 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#545935} wpt-commits: 92461700073cb989bf1df2deada5413b06647b80 wpt-pr: 10173 wpt-commits: 92461700073cb989bf1df2deada5413b06647b80 wpt-pr: 10173
e025792ad0b2e55247db64ba924c4f52a6b4a5c0: Bug 1448335 [wpt PR 10157] - [css-typedom] Add support for the *-gap properties., a=testonly
Rune Lillesveen <futhark@chromium.org> - Mon, 09 Apr 2018 18:14:09 +0000 - rev 413654
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1448335 [wpt PR 10157] - [css-typedom] Add support for the *-gap properties., a=testonly Automatic update from web-platform-tests[css-typedom] Add support for the *-gap properties. Bug: 820299 Change-Id: I596113eeea7d4c13cf689364744bff7c261f93d3 Reviewed-on: https://chromium-review.googlesource.com/978247 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545896} wpt-commits: 06f77f6bfaa86f3643a79f1ec2c49c6b6955cf18 wpt-pr: 10157 wpt-commits: 06f77f6bfaa86f3643a79f1ec2c49c6b6955cf18 wpt-pr: 10157
4cfcb3612183d4dd0bfe26a40103525b8d6aa33d: Bug 1449011 [wpt PR 10184] - Better explain test execution in resources/test/README, a=testonly
Robert Ma <bob1211@gmail.com> - Mon, 09 Apr 2018 18:13:33 +0000 - rev 413653
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1449011 [wpt PR 10184] - Better explain test execution in resources/test/README, a=testonly Automatic update from web-platform-testsBetter explain test execution in resources/test/README wpt-commits: f497de835233b7d8ea79a39fa89cb766d1c12b75 wpt-pr: 10184 wpt-commits: f497de835233b7d8ea79a39fa89cb766d1c12b75 wpt-pr: 10184
76971d866c6999ca47afedbc7c428b513b2cbb10: Bug 1446130 [wpt PR 10054] - [css-layout-api] Allow LayoutChild(ren) to be laid out., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Mon, 09 Apr 2018 18:13:04 +0000 - rev 413652
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1446130 [wpt PR 10054] - [css-layout-api] Allow LayoutChild(ren) to be laid out., a=testonly Automatic update from web-platform-tests[css-layout-api] Allow LayoutChild(ren) to be laid out. This allows a LayoutChild to have layout performed on it, which will return a Fragment - with the correct inline and block sizes. These Fragments cannot be positioned yet, (next patch). The LayoutChild will be laid out with an available inline/block size of zero by default, and optionally can accept a fixed-inline/block size, which it must respect. Bug: 726125 Change-Id: Ie4386b8f6cd6ccec3f9e52ff332322101058836d Reviewed-on: https://chromium-review.googlesource.com/962870 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#545845} wpt-commits: 7988e1756539bcdf39ec2102b99e0671c44d503c wpt-pr: 10054 wpt-commits: 7988e1756539bcdf39ec2102b99e0671c44d503c wpt-pr: 10054
1c178deec30f8b05ed3300f0b0e59efcc31fe240: Bug 1436404 [wpt PR 9418] - [css-sizing] Intrinsic percentage non-replaced widths, a=testonly
fantasai <fantasai.bugs@inkedblade.net> - Mon, 09 Apr 2018 18:12:33 +0000 - rev 413651
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1436404 [wpt PR 9418] - [css-sizing] Intrinsic percentage non-replaced widths, a=testonly Automatic update from web-platform-tests[css-sizing-3] Add tests for intrinsic size contribution (width/inline-size) of non-replaced blocks with percentage widths. See https://github.com/w3c/csswg-drafts/issues/1132 wpt-commits: 5957997833c0c2dacbcf29b2e2eebd0a7c096c91 wpt-pr: 9418 wpt-commits: 5957997833c0c2dacbcf29b2e2eebd0a7c096c91 wpt-pr: 9418
ef9bce229bcce13d8bbbecd8d51d388adb9c0702: Bug 1447881 [wpt PR 10134] - [css-typed-om] support block-size and inline-size, a=testonly
Hwanseung Lee <hs1217.lee@samsung.com> - Mon, 09 Apr 2018 18:12:06 +0000 - rev 413650
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1447881 [wpt PR 10134] - [css-typed-om] support block-size and inline-size, a=testonly Automatic update from web-platform-tests[css-typed-om] support block-size and inline-size block-size[1], inline-size[2], max-block-size[3], max-inline-size[4], min-block-size[5], min-inline-size[6] are added to support in whitelist. and test file are also added. [1]https://drafts.csswg.org/css-logical-1/#propdef-block-size [2]https://drafts.csswg.org/css-logical-1/#propdef-inline-size [3]https://drafts.csswg.org/css-logical-1/#propdef-max-block-size [4]https://drafts.csswg.org/css-logical-1/#propdef-max-inline-size [5]https://drafts.csswg.org/css-logical-1/#propdef-min-block-size [6]https://drafts.csswg.org/css-logical-1/#propdef-min-inline-size Bug: 820299 Change-Id: I97c589deea28bfedc82ec1b1686ceaf9979cb95e Reviewed-on: https://chromium-review.googlesource.com/973561 Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#545802} wpt-commits: a890989795f8c8d005db4fd5fe859b171c6c1d98 wpt-pr: 10134 wpt-commits: a890989795f8c8d005db4fd5fe859b171c6c1d98 wpt-pr: 10134
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip