tree 62711ca5f5c3324d47756f3f674509ee44a39532
parent a4e1845df9d2a57cdce62b534c4874e11ecbf155
author Ian Kilpatrick <ikilpatrick@chromium.org> 1651256688 -0700
committer Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> 1651257200 -0700

[BlockFragmentation] Split null/max MinimalSpaceShortage representation

Previously we'd represent the "null" MinimalSpaceShortage as LayoutUnit::Max().

This causes us to be "confused" when we have a space-shortage which is
also LayoutUnit::Max(). This changes the representation to use
absl::optional<LayoutUnit> for the algorithm parts, and internally
just a LayoutUnit (similar to the current layout-result), with "null"
being kIndefiniteSize.

Bug: 1314866
Change-Id: I27be96fddcc6dba260a3b7531483b168fd75e393
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3606583
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#997787}