STR: 1. Load attached testcase. FIREFOX AND WEBKIT RESULTS: Cyan area goes below the float. CHROME RESULTS: Cyan area goes to the right of the float. Filing this to track a known behavior-difference at least -- though I think Firefox/WebKit are probably correct in terms of how `stretch` is supposed to behave (and the prefixed equivalents which ideally should match it). The spec text for `stretch` here... https://drafts.csswg.org/css-sizing-4/#valdef-width-stretch https://drafts.csswg.org/css-sizing-4/#stretch-fit-sizing ...essentially says the used size is "he length necessary to make its outer size as close to filling the containing block as possible while still respecting the constraints imposed by min-height/min-width/max-height/max-width." It goes into additional detail but doesn't have any special cases regarding floats or clearance. So, in this case, it should behave equivalent to `width:100%` which matches the Firefox/WebKit behavior. Hence: probably not a bug on our side, though potentially worth tracking in case Chrome doesn't fix it and there's ends up being interop impact.
Bug 1920634 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
STR: 1. Load attached testcase. FIREFOX AND WEBKIT RESULTS: Cyan area goes below the float. CHROME RESULTS: Cyan area goes to the right of the float. Filing this to track a known behavior-difference at least -- though I think Firefox/WebKit are probably correct in terms of how `stretch` is supposed to behave (and the prefixed equivalents which ideally should match it). The spec text for `stretch` here... https://drafts.csswg.org/css-sizing-4/#valdef-width-stretch https://drafts.csswg.org/css-sizing-4/#stretch-fit-sizing ...essentially says the used size is "he length necessary to make its outer size as close to filling the containing block as possible while still respecting the constraints imposed by min-height/min-width/max-height/max-width." It goes into additional detail but doesn't have any special cases regarding floats or clearance. So, in this case, it should behave equivalent to `width:100%` which matches the Firefox/WebKit behavior. Hence: probably not a bug on our side, though potentially worth tracking in case Chrome doesn't fix it and there ends up being interop impact.