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

Re: [csswg-drafts] [css-inline-3] 'vertical-align: middle' on table cells (#5234)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 28 Jul 2020 22:48:34 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-665333401-1595976513-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-inline-3] 'vertical-align: middle' on table cells`, and agreed to the following:

* `RESOLVED: top and bottom take precedence over middle`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-inline-3] 'vertical-align: middle' on table cells<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5234<br>
&lt;dael> fantasai: has top keyword and bottom keyword which are special b/c don't work off baseline. THey shift based on total linebox size.<br>
&lt;dael> fantasai: Also has middle which is x-middle baseline and aligns to x-middle of parent. Same as alphabetic<br>
&lt;dael> fantasai: We also have vertical-align top, middle, bottom all behave completely unrelated to inline layout and they are basically start, center and end. By splitting to longhand it means we have to map to magic. Middle is part of alignment-baseline and top and bottom are line relative<br>
&lt;dael> fantasai: Can spec vertical-align top middle on a table cell. What does that mean?<br>
&lt;dael> fantasai: I prefer top and bottom take precedence<br>
&lt;dbaron> sounds fine to me<br>
&lt;dael> AmeliaBR: Did debate recently about which longhand top and bottom go to. One solution is move them into other longhand to solve this one issue<br>
&lt;dael> AmeliaBR: It would meant that alignment-baseline controls table alignment b/c that makes no less sense than anything else<br>
&lt;dael> florian: THink we had reasons to put in longhand we picked<br>
&lt;dael> fantasai: B/c not possible to combine top or bottom with shift. Can in theory with everything else<br>
&lt;dael> fantasai: I don't have a strong feeling about this. Don't know if anyone else does<br>
&lt;dael> florian: To extent we keep in longhand your proposal seems reasonable. Should they be moved is separate<br>
&lt;dael> fantasai: Right, we can re-open that issue and tag for discussion<br>
&lt;dael> fantasai: This top and bottom take precedence over middle<br>
&lt;florian> s/keep in longhand/keep in this longhand/<br>
&lt;dael> Rossen_: Other comments or objections?<br>
&lt;fantasai> s/we can/anyone who wants can/<br>
&lt;dael> RESOLVED: top and bottom take precedence over middle<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5234#issuecomment-665333401 using your GitHub account
Received on Tuesday, 28 July 2020 22:48:36 UTC

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