Re: [csswg-drafts] [css-align-3] safe vs unsafe defaults for block containers (#8992)

The CSS Working Group just discussed `[css-align-3] safe vs unsafe defaults for block containers`, and agreed to the following:

* `RESOLVED: default behavior for align-content on block containers is safe`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> fantasai: currently when you apply align-/justify-content to flex/grid they are unsafe, but ua's are not supposed to shift stuff off the unscrollable region, but nobody implements that<br>
&lt;emilio> ... for safe centering if the content is more than the container you clip to the top<br>
&lt;emilio> ... the spec behavior is technically limit by the scroll-container edges but nobody implements that<br>
&lt;emilio> ... the align is spec'd to also apply to block containers<br>
&lt;emilio> ... currently nobody implements that except the Firefox checkout on my laptop<br>
&lt;emilio> ... there are some concerns about web compat but also whether unsafe centering is right for block<br>
&lt;bramus> q+<br>
&lt;emilio> ... I think for block layout in general safe centering by default makes more sense<br>
&lt;emilio> ... also reduces the chances of a compat issue<br>
&lt;emilio> ... proposal is that for block containers we default to safe alignment<br>
&lt;emilio> Rossen_: this would be in both directions right?<br>
&lt;emilio> fantasai: block containers don't support justify-content, just align-content<br>
&lt;iank_> q+<br>
&lt;Rossen_> ack bramus<br>
&lt;emilio> bramus: the default grid/flex has definitely tripped off authors<br>
&lt;emilio> ... so +1 but people might rely on unsafe alignment?<br>
&lt;emilio> fantasai: not implemented anywhere yet<br>
&lt;Rossen_> ack iank_<br>
&lt;emilio> iank_: this seems fine overall<br>
&lt;oriol> q+<br>
&lt;emilio> ... we find that for table cells where they fall back to vertical-alignment: middle it uses unsafe<br>
&lt;emilio> ... as long as it's not messing with table cells seems fine<br>
&lt;emilio> ... I don't think it's a huge compat mitigation, the biggest risk is the new bfc behavior<br>
&lt;emilio> oriol: I'm reading that you're proposing it for block containers that are not scroll-container<br>
&lt;emilio> ... do you want to keep this distinction? If so, why?<br>
&lt;emilio> fantasai: for block containers that are scroll containers you don't have this unsafeness because you don't have overflow<br>
&lt;emilio> ... your entire scrollable region is aligned and the initial scroll position changes<br>
&lt;emilio> ... per spec, you're not supposed to shift the content<br>
&lt;emilio> ... you're supposed to change the initial scroll position<br>
&lt;emilio> oriol: I also wanted to ask that you mentioned that the default is unsafe, but wasn't there some magic if neither was specified?<br>
&lt;emilio> fantasai: yeah, which nobody implements. we wouldn't do that for blocks and just default to safe which is also simplere<br>
&lt;emilio> s/simplere/simpler<br>
&lt;emilio> RESOLVED: default behavior for align-content on block containers is safe<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8992#issuecomment-1642562513 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 July 2023 18:30:15 UTC