Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 0906e08508debe46c7e89f44a688675085c43eff
https://github.com/WebKit/WebKit/commit/0906e08508debe46c7e89f44a688675085c43eff
Author: Sammy Gill <[email protected]>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
A
LayoutTests/imported/w3c/web-platform-tests/css/css-grid/grid-definition/grid-template-columns-rows-resolved-values-002-expected.txt
A
LayoutTests/imported/w3c/web-platform-tests/css/css-grid/grid-definition/grid-template-columns-rows-resolved-values-002.html
M Source/WebCore/layout/integration/grid/LayoutIntegrationGridLayout.cpp
M Source/WebCore/rendering/RenderGrid.cpp
M Source/WebCore/rendering/RenderGrid.h
Log Message:
-----------
[GFC][Integration] Resolved track listing should be properly reflected
https://bugs.webkit.org/show_bug.cgi?id=319281
rdar://182120327
Reviewed by Alan Baradlay.
In 317067@main we had RenderGrid store its resolved track listing as a
specific output of layout instead of trying to reverse engineer it from
the positions vector, gap sizes, etc.
In this patch we adopt the new behavior and make sure that any content
that runs through GFC can still report its resolved track listing
correctly in the same way. This is done by just having the integration
logic set the value in the same way legacy grid layout does on the end
of layout.
* Source/WebCore/rendering/RenderGrid.cpp:
(WebCore::RenderGrid::layoutGrid):
Now that GFC also writes to the same structure we can have legacy grid
layout invalidate it even earlier.
Canonical link: https://commits.webkit.org/317165@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
