- From: davidsgrogan via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Dec 2020 21:19:31 +0000
- To: public-css-archive@w3.org
> In particular, the intent of the change was 'to make the cyclic percentage rules that zero out percentages apply to automatic minimum size calculations Agreed. And agreed that Chrome's current behavior obeys this change. But I haven't seen anything that explains the motivation behind the change. As in, why should this replaced-element exception * in the min-content contribution algorithm * for cyclic cases * that was required for compat apply to * the automatic minimum size algorithm * for _non_-cyclic cases * when there is no compat requirement? They seem like different situations 3x over. What's the benefit to web devs here? -- GitHub Notification of comment by davidsgrogan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5665#issuecomment-742066670 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 December 2020 21:19:33 UTC