-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Apply-order must not matter for grid-template-[areas,rows,columns]
We can currently get two different ComputedStyles depending on which order we apply certain grid-* properties in. This must not happen in Blink, even if it doesn't result in a web-facing change, because we have optimizations that rely on sanity in this area. The issue is that the Apply functions for grid-template-[columns,rows] look at the (potentially work-in-progress) computed value of grid-template-area, and uses this to generate implicit named lines. However, we also do this implicit named line generation in GridTemplateAreas::ApplyValue, and store those in a separate field on ComputedStyle. As far as I can tell, in the all the places we access ComputedGridTrackList::named_grid_lines, we also already check ComputedStyle::ImplicitNamedGrid*Lines, which leads me to believe that adding the implicit named lines during GridTemplate[Columns,Rows]:: Apply is actually redundant. The only exception is InspectorHighlight, which needs to be extended to also include the implicit lines. Fixed: 1320659 Change-Id: I1a36a245559a591cec29b954942c384cf98495b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3636378 Reviewed-by: Changhao Han <changhaohan@chromium.org> Reviewed-by: Ana Sollano Kim <ansollan@microsoft.com> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/main@{#1001716}
- Loading branch information
Showing
6 changed files
with
188 additions
and
92 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.