Apply |PostLayout| to |LayoutBox| instead of |LayoutBlockFlow|
|PostLayout| was limited to |LayoutBlockFlow| because crbug.com/965639 could happen only to|LayoutBlockFlow|, but following conditions have changed: * Only |LayoutBlockFlow| could be relayout boundary, until r772560 <crrev.com/c/2219312>. * Only |LayoutBlockFlow| was laid out by LayoutNG, until |LayoutNGFlexibleBox| inherits from |LayoutBlock|. This patch changes |PostLayout| to work for |LayoutBox|. In doing so, two changes were made: 1. |CurrentFragment| is replaced with |GetPhysicalFragment| because the former is not available for |LayoutBox|. 2. Stopped checking |IsRelayoutBoundary|. Though it is the only case crbug.com/965639 can happen as far as we're aware of, checking |NGPhysicalFragment| is more essential and sufficient. The change 1 also helps <crbug.com/1061423>, but we may need different approach to support block fragmentation. Bug: 1102151, 965639 Change-Id: Id83be614066392a4c58c8b03bd16ee57ad82e145 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302984Reviewed-by:David Grogan <dgrogan@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#789656}
Showing
Please register or sign in to comment