- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jul 2017 16:22:30 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Should last-baseline's fallback alignment be safe or unsafe?`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Should last-baseline's fallback alignment be safe or unsafe?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1611<br> <dael> Rossen_: We discussed last week, but didn't resolve as far as I remember.<br> <dael> Rossen_: We wanted to gather any additional thoughts on GH. There were no updates. Do we feel like we have enough to resolve or do wew leave to F2F?<br> <dael> Rossen_: Last week we couldn't get to a solution going back and forth a few times.<br> <dael> Rossen_: We didn't resolve due to time constraints. But we also had this back and forth about if this makes the most sense and the most consistant with other alignments and their default behavior in overconstraint scenarios.<br> <dael> fantasai: Seems we didn't have consensus b/c good arguments in both directions.<br> <dael> fantasai: Prob what we need is actual use case scenarios to come up with a r eason for one being better.<br> <dael> Rossen_: As I mentioned, I can be persuaded either way. I favor consistancy and in thsi case there was some inconsistancywith the way fallback occurs for safe and unsafe b/c descrpency between basline-laign and align end.<br> <dael> fantasai: There's 2 kinds of align. safe and unsafe. We could be consistant with either one.<br> <dael> Rossen_: Right.<br> <dael> fantasai: I'm okay defering to F2F.<br> <dael> fantasai: I'm hoping at F2F people will h ave something concrete for one or the other.<br> <dael> Rossen_: I don't mind<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1611#issuecomment-318106344 using your GitHub account
Received on Wednesday, 26 July 2017 16:22:30 UTC