[LayoutNG] Fix clusterfuzz crash
Using empty Optional<MinMax> to indicate that MinMax value should not matter caused trouble with ng_length_utils ResolveInlineLengthInternal, when max-width was fit-content. Use MinMax(0, LayoutUnitMax) to indicate intrinsic size does not matter instead. It accomplishes the same goal, computed size does not get clamped by intrinsic. I've also tested running it with width:max-content out of fear that we might end up with too wide OOF, but that did not happen. Bug: 1010798 Change-Id: Ife11b3d9637be91cc0648b7f8485af51f07108bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1837118 Commit-Queue: Aleks Totic <atotic@chromium.org> Auto-Submit: Aleks Totic <atotic@chromium.org> Reviewed-by:Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#702525}
Showing
Please register or sign in to comment