- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Jun 2017 17:09:33 +0000
- To: public-css-archive@w3.org
> What I’m still trying to process is how inline-before-block “breaks consensus with CSS itself”. It seems split; 2-value shorthands are inline-first while 4 value-shorthands are block-first. Right, *only* 2-value shorthands are inline-first. The 4-value shorthands are block-first. You were proposing that we make 4-value logical shorthands inline-first, to match some outside technologies; that is inconsistent with CSS, which is clear on where 4-value shorthands start. I then also noted that CSS is inconsistent with itself with respect to 2 values: properties that *only* take two values do inline-first, while 4-value properties that you only specify two values for take block-first. We can't fix this pattern in the physical properties, but we can at least make them work consistently in the logical properties. (Making both 2-value and 4-value logical properties do inline-first would also keep them internally consistent, but the argument in my first paragraph suggests that this is the wrong answer for 4-value properties.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1500#issuecomment-307446086 using your GitHub account
Received on Friday, 9 June 2017 17:09:39 UTC