You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Safari currently has hysteresis[1] in its calculation (e.g. resize the browser window for the above example). So ends up in two different states.
For a multi-line flexbox the differing sizes looks bad to me in this example, IMO it'd be better not to consider trimming at this stage of computing the hypothetical, etc. And instead only consider the trim margins after line-breaking, and flexing has been performed.
[1] Using the value of a previous layout in the next layout.
The text was updated successfully, but these errors were encountered:
Flexbox does a bunch of calculations before it knows what line an item will end up on (e.g. computing the hypothetical size).
Margins can affect these calculations - for example:
Safari currently has hysteresis[1] in its calculation (e.g. resize the browser window for the above example). So ends up in two different states.
For a multi-line flexbox the differing sizes looks bad to me in this example, IMO it'd be better not to consider trimming at this stage of computing the hypothetical, etc. And instead only consider the trim margins after line-breaking, and flexing has been performed.
[1] Using the value of a previous layout in the next layout.
The text was updated successfully, but these errors were encountered: