W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2017

[csswg-drafts] [css-align][css-flexbox][css-grid] partial implementations of space-evenly in grid but not flexbox

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Tue, 04 Apr 2017 10:19:40 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-219203798-1491301178-sysbot+gh@w3.org>
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-align][css-flexbox][css-grid] partial implementations of space-evenly in grid but not flexbox ==
See this twitter conversation: https://twitter.com/lajava77/status/849182533791227904

TL;DR: Safari and Chrome ship `justify-content: space-evenly`, but it only works in grid, not in flexbox.

In their implementations, in flexbox, it falls back to the same behavior as `flex-start`. But since it parses fine, you cannot use the cascade or `@support` to provide a different fallback.

The real solution is for both browsers to fix this by completing their implementation, but my question is:
- should they unship `justify-content: space-evenly` until then (even though it works fine in grid)?
- If no, as a stopgap measure until full implementation, should they make it behave like `justify-content: space-around` (most similar) or `justify-content: center` (specified as the fallback alignment, for different situations)?

Should the spec say something about this particular kind of partial implementations, besides what's already in https://drafts.csswg.org/css-align/#conform-partial

@mrego @javifernandez @tabatkins @fantasai 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1167 using your GitHub account
Received on Tuesday, 4 April 2017 10:19:47 UTC

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