- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Dec 2024 20:39:02 +0000
- To: public-css-archive@w3.org
Chatting with David a little, there are 3 bad scenarios: 1. Overflow of a single element of its parent is bad (the cases talked about in comment 2 - https://github.com/w3c/csswg-drafts/issues/11044#issuecomment-2419902622). 2. Height differences of children with the exact same styling (in block flow) is bad. (case talked about in my comment - https://github.com/w3c/csswg-drafts/issues/11044#issuecomment-2518616089 ). Similarly height differences depending on sibling presence is bad for the dynamic insertion/removal usecase. 3. Not stretching to the parent is bad (again case talked about in comment 2, Blink's behaviour for "magenta" case). I don't think we can solve all three of these bad scenarios, which leaves how you choose to rank them. My personal rank is "1", "2", "3". (and the current algorithm is ok with sometimes breaking "3" at the moment). Based on my personal rank of prioritizing "1" & "2" over "3", my preferred solution is Blink's current implementation. E.g. taking the constraint of "2" you can't use any sibling information, which just leaves information provided by the parent style directly. Ian -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11044#issuecomment-2532837465 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 December 2024 20:39:03 UTC