Bug 1713192 [wpt PR 29144] - Add |SideEffectsDisabled| for MinMax-after-layout, a...
commitf027b144558f96606ee01df82142d2745a40de03
authorKoji Ishii <kojii@chromium.org>
Mon, 7 Jun 2021 14:07:06 +0000 (7 14:07 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Tue, 8 Jun 2021 19:05:18 +0000 (8 19:05 +0000)
treec7adff98111262e60879d344065ea0c9832e2b52
parentb1d9609e7e46be2244ebd9e8157c2abede1ec99d
Bug 1713192 [wpt PR 29144] - Add |SideEffectsDisabled| for MinMax-after-layout, a=testonly

Automatic update from web-platform-tests
Add |SideEffectsDisabled| for MinMax-after-layout

Computing MinMax after layout was prohibited in legacy. NG can
do this, except that it copies the fragment data back to the
|LayoutObject| tree, update |PaintLayer|, scroll bar
propoerties, etc.

This patch adds |SideEffectsDisabled| to indicate the
situation, and change |NGBlockNode::FinishLayout| to not to
update the |LayoutObject| tree and other global states.

This is the case 1 of the discussion doc:
https://docs.google.com/document/d/1HkMwnfr-JbP2SE0ktYalkeAutwciuy-GftLs3TOnBcI/edit?usp=sharing

Bug: 1213358
Change-Id: I352d73447e1795510f3673abb8c2dc532afea532
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2912340
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#887785}

--

wpt-commits: 6494c279e6c4395373a4e737677ed822beb9949c
wpt-pr: 29144
testing/web-platform/tests/css/css-writing-modes/crashtests/orthogonal-scroll-percent-height-crash.html [new file with mode: 0644]