New issue
Advanced search Search tips

Issue 721319 link

Starred by 3 users
Status: Available
Owner: ----
Cc:
jfernan...@igalia.com
r...@igalia.com
svil...@igalia.com
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

[css-grid] Wrong intrinsic track size due to min-contribution change after the first pass of the grid track sizing algorithm

Project Member Reported by r...@igalia.com, May 11 2017 
The text on the spec (https://drafts.csswg.org/css-grid/#algo-overview):
"
 Then, if the min-content contribution of any grid items
 have changed based on the row sizes calculated in step 2,
 steps 1 and 2 are repeated with the new min-content contribution
 and max-content contribution (once only).

 > This cycle is necessary for cases where the inline size of
 > a grid item depends on the block size of its grid area.
 > Examples include wrapped column flex containers
 > (flex-flow: column wrap), orthogonal flows (writing-mode),
 > and multi-column elements.
"

Now we're doing the 2nd pass if we've any orthogonal item,
but we're not doing it in the case of a Flexbox grid item.

Check the attached example and the current and expected outputs.
bug-column-flexbox-grid-item.html
759 bytes View Download
bug-column-flexbox-grid-item-current.png
10.0 KB View Download
bug-column-flexbox-grid-item-expected.png
8.4 KB View Download
Project Member

Comment 1 by sheriffbot@chromium.org, May 11 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by jfernan...@igalia.com, May 11 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment