Commit 0a0a19e7 authored by Ian Kilpatrick's avatar Ian Kilpatrick Committed by Commit Bot

[LayoutNG] Acutally use CurrentFragment within LayoutNGMixin::Paint.

There should be no behaviour change.

Change-Id: Ic9b22f18358779f9808c7e2aa2f37422e9696936
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976939Reviewed-by: default avatarChristian Biesinger <cbiesinger@chromium.org>
Reviewed-by: default avatarAleks Totic <atotic@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726570}
parent 3b874bcf
...@@ -40,10 +40,8 @@ void LayoutNGMixin<Base>::Paint(const PaintInfo& paint_info) const { ...@@ -40,10 +40,8 @@ void LayoutNGMixin<Base>::Paint(const PaintInfo& paint_info) const {
return; return;
} }
if (const NGLayoutResult* result = Base::GetCachedLayoutResult()) { if (const NGPhysicalBoxFragment* fragment = CurrentFragment())
NGBoxFragmentPainter(To<NGPhysicalBoxFragment>(result->PhysicalFragment())) NGBoxFragmentPainter(*fragment).Paint(paint_info);
.Paint(paint_info);
}
} }
// The current fragment from the last layout cycle for this box. // The current fragment from the last layout cycle for this box.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment