Dump LayoutNG fragment roots that are inside legacy subtrees.
Previously we'd just stop when reaching a legacy fragment (since such fragments are always childless). But descendants of a legacy object may re-enter NG layout further down the road (this is the case for tables and grid, for instance), and dumping those fragment subtrees may also be useful. Example (assuming that tables are laid out by the legacy engine): <!DOCTYPE html> <div style="display:table;"> <div>HELLO</div> </div> NGPhysicalFragment::DumpFragmentTree() will now include the DIV child of the table: .:: LayoutNG Physical Fragment Tree ::. Box (block-flow-root block-flow)(self paint) offset:unplaced size:800x34 LayoutNGBlockFlow HTML Box (block-flow) offset:8,8 size:784x18 LayoutNGBlockFlow BODY Box (block-flow-root legacy-layout-root) offset:0,0 size:53x18 LayoutTable DIV (NG fragment root inside legacy subtree:) Box (block-flow-root block-flow) offset:unplaced size:53x18 LayoutNGTableCell (anonymous) Box (block-flow children-inline) offset:0,0 size:53x18 LayoutNGBlockFlow DIV NGPhysicalLineBoxFragment offset:0,0 size:52.4375x18 NGPhysicalTextFragment 'HELLO' offset:0,0 size:52.4375x17 Change-Id: I95c63181f1d716bd8f79dfb25b9e31fdde49545e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617845Reviewed-by:Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#842458}
Showing
Please register or sign in to comment