- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Mar 2023 19:34:56 +0000
- To: public-css-archive@w3.org
>I don't think it's well-defined what it means to satisf[y] the requirements of place-content: end alignment, though. To the extent that it is well-defined, it seems the spec says to do nothing in this case. Yeah I'd probably agree with that. I previously advocated for writing down the "inflow-bounds" for each layout method - but I think others said the `place-content: end` alignment was equivalent to this. https://github.com/w3c/csswg-drafts/issues/129#issuecomment-701519671 > Haven't looked closely at this yet, but if it's relevant, we haven't landed our changes for https://github.com/w3c/csswg-drafts/issues/129 yet (https://bugzilla.mozilla.org/show_bug.cgi?id=1768921 ). The main thing to keep in mind is that this isn't directly adding margins, just the padding at the end of the inflow-bounds. @dholbert - What do you think of removing the margin-clause entirely? E.g. For flex/grid items, firefox&webkit are only applying the margins if the grid/flex container is also a scroll container, and since we have the inflow-bounds padding-edge, its applicability is very limited now (need to create very complex cases to actually trigger the behavour difference). -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8660#issuecomment-1492495021 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 March 2023 19:34:57 UTC