Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 7e86f405c777ba9e632c23261cf2af96a40b5c60
https://github.com/WebKit/WebKit/commit/7e86f405c777ba9e632c23261cf2af96a40b5c60
Author: Alan Baradlay <[email protected]>
Date: 2026-07-15 (Wed, 15 Jul 2026)
Changed paths:
M Source/WebCore/rendering/RenderFlexibleBox.cpp
M Source/WebCore/rendering/RenderFlexibleBox.h
Log Message:
-----------
[cleanup] Snapshot the flex item's main-axis-is-inline-axis flag on
FlexLayoutItem
https://bugs.webkit.org/show_bug.cgi?id=318602
Reviewed by Antti Koivisto.
FlexLayoutItem now snapshots whether the flex container's main axis is the
item's inline
axis, mirroring the mainAxisBorderAndPadding / crossAxisBorderAndPadding
fields. It is
populated at construction from the same comparison the FlexLayoutUtils query
makes (the
container's flow horizontal-ness against the item's writing mode), so it is a
pure immutable
per-item fact with no layout-state dependency. This is the positive sense of
the flag FFC
bakes onto LogicalFlexItem as isOrthogonal.
The twelve core-sizing sites that reach the item now read the field instead of
calling
flexLayoutUtils().mainAxisIsFlexItemInlineAxis(renderer). The other callers
keep the util
query: they run against a bare renderer with no FlexLayoutItem (the baseline
candidates, the
public percentage-resolution query, setOverridingMainSizeForFlexItem, and the
ScopedCrossAxisOverrideForFlexItem constructor / performBaselineAlignment
lambda).
No change in behavior.
* Source/WebCore/rendering/RenderFlexibleBox.cpp:
* Source/WebCore/rendering/RenderFlexibleBox.h:
Canonical link: https://commits.webkit.org/317235@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
