- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Jun 2021 16:58:14 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `baseline-alignment and auto margins`, and agreed to the following: * `RESOLVED: alignment via auto margins disables content baseline-alignment the same way as align-self values with the same effect` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: baseline-alignment and auto margins<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/5923<br> <emeyer> fantasai: The interaction isn’t well defined. We found there’s a lot missing about grid and auto margins. We made a non-normative section normative. We brought some alignment into harmony with flexbox.<br> <emeyer> fantasai: When you have content baseline alignment across multiple items, and you’re trying to add padding, the ‘align-self’ property can move the box.<br> <emeyer> fantasai: If boxes are moved, baseline alignment gets weird. We have some working in alignment that says you have to have a coordinating alignment, start or end.<br> <emeyer> fantasai: We didn’t account for how auto margins can move boxes.<br> <emeyer> fantasai: Option 1, we require a coordinated alignment effect. If the auto margin cause the box to be centered, baseline alignment is diabled.<br> <emeyer> fantasai: Option 2, any auto margins diable baseline alignment.<br> <emeyer> fantasai: We went with option 1 but are open to other options.<br> <fantasai> iank_: We don't implement content baseline alignment yet<br> <fantasai> iank_: but I think it sounds fine<br> <fantasai> iank_: for self-alignment though, any auto margins don't participate in baseline alignment, right?<br> <emeyer> fantasai: If that’s what’s implemented, the spec should say so.<br> <fantasai> iank_: If we have align-self: baseline and any auto margin, we ignore that align-self<br> <fantasai> fantasai: Right, they're both trying to align the box, so have to pick one<br> <fantasai> iank_: but for content alignment, this seems fine<br> <fantasai> iank_: One thing I might need to check is, if they participate in the propagation of a baseline<br> <fantasai> iank_: but that might be a separate issue...<br> <fantasai> [discussion of javier's comments, possible mixing up self- vs content-alignment causing confusion]<br> <dholbert> which option are we proposing?<br> <dholbert> (1 vs 2)<br> <fantasai> I think we're proposing 1, unless anyone has a problem with 2<br> <dholbert> (I'm fine with either, I think)<br> <fantasai> s/with 2/with it<br> <fantasai> Rossen: Anyone else with an opinion?<br> <fantasai> proposed: alignment via auto margins disables content baseline-alignment the same way as align-self values with the same effect<br> <fantasai> RESOLVED: alignment via auto margins disables content baseline-alignment the same way as align-self values with the same effect<br> <fantasai> Rossen: if Javier or Tab has concerns, can come back to it later<br> <emeyer> [search for a topic that can be covered in ~3 minutes]<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5923#issuecomment-867005738 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 June 2021 16:58:34 UTC