W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2020

Re: [csswg-drafts] [css-align-3] Punt baseline-alignment to level 4 (#4660)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 May 2020 21:42:00 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-625512124-1588887719-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-align-3] Punt baseline-alignment to level 4 #4660`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-align-3] Punt baseline-alignment to level 4 #4660<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4660<br>
&lt;dael> fantasai: We can punt. We had resolved to push baseline align out to L4. Looked into it and I think it's awk and confusing.<br>
&lt;dael> fantasai: Baseline keyword is part of initial flexbox keywords. Impl across all browsers. Pushing I think is confusing to authors<br>
&lt;dael> fantasai: A little uncomfortable with that resolution. I don't think we're that far from fixing remaining baseline issues. If we started from scratch sure but since it's been in flexbox from the beginning hesitant to pull it out<br>
&lt;dael> Rossen_: Opinions? Concerns?<br>
&lt;astearns> would prefer to keep it in level 3<br>
&lt;dael> fantasai: Main concern is there's some issues with definition of intrinsic sizing and sizing algos interacting with baseline alignment. Not sure how to deal. Not clear errors in spec. THat's main thing we're stuck on.<br>
&lt;Rossen_> q<br>
&lt;dael> Rossen_: I know of some issues that will be...or dependencies from grid. What other sizing algo affected?<br>
&lt;dael> fantasai: Flex, grid, and [missed]<br>
&lt;dael> florian: Tables<br>
&lt;dael> fantasai: Not aware of significant concerns from impl about implementability. That's the one thing we're stuck on. Everything else is fixable soonish so we can take whole L3 to CR<br>
&lt;dael> fantasai: Just my thoughts. THat's why I haven't edited it in<br>
&lt;dael> dbaron: Alternatives in space of keeping baseline alignment in but saying x is undefined<br>
&lt;dael> fantasai: Not sure what should be undefined.<br>
&lt;dael> dbaron: I'd need to dig in more.<br>
&lt;dael> dbaron: Issue 1409 is about how baseline alignment changes intrinsic sizes. Example might be spec saying that it's undefined. Need to dig more to see if it makes sense<br>
&lt;dael> fantasai: Would you be willing to take a look into what it would be acceptable for spec to say?<br>
&lt;dael> dbaron: I can look<br>
&lt;dael> Rossen_: So we hold on pushing to L4 until then?<br>
&lt;dael> fantasai: Yes, goal is dbaron to come back to something and we take it to CR<br>
&lt;dael> action dbaron take a look at baseline alignment and how to keep it in L3 by undefining things<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4660#issuecomment-625512124 using your GitHub account
Received on Thursday, 7 May 2020 21:42:02 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:06 UTC