- From: Rossen Atanassov via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Mar 2018 04:36:46 +0000
- To: public-css-archive@w3.org
Some of the original reasoning for the behavior (at least looking through some old test cases) suggests this was intended for scenarios where a spanning header was supposed to influence the size of columns in an article. I don't believe we have a strong reason and/or content that depends on this behavior at this point so we could go either way. Assuming we want to keep the exception, it'd be good to explore tweaking the heuristic with something like: - Spanners that cross tracks that have content-based mins AND flexible maxes only contribute content sizes to those tracks; otherwise they participate normally. Since flexible tracks now have auto minimums by default, this will ensure that spanners crossing flexible tracks only contribute to non-flexible tracks if all the flexible tracks have explicit fixed mins. It seems like that embodies the spirit of the original heuristic (spanners typically rely on flexible tracks to fit) while also satisfying the requirement that items crossing content-sized tracks shouldn’t overflow their tracks. -- GitHub Notification of comment by atanassov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2177#issuecomment-376394503 using your GitHub account
Received on Tuesday, 27 March 2018 04:37:27 UTC