W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2016

Re: [csswg-drafts] [css-align] Add shorthands for alignment properties

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Tue, 01 Nov 2016 16:49:34 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-257620722-1478018973-sysbot+gh@w3.org>
Yeah, as I said above, there's both the ambiguity of something like:
`place-content: end stretch end`
which could mean:
`align-content: end stretch`
`justify-content: end`
or
`align-content: end`
`justify-content: stretch end`

and the ambiguity about if the value is a single value or not:
`place-content: end stretch`
could mean (as a single value):
`align-content: end stretch`
`justify-content: end stretch`
or (as two values)
`align-content: end`
`justify-content: stretch`

(and there are many variations of those ambiguities of course...)

So, my preference is to use `/` as the separator because it can 
represent all
values unambiguously.  If you choose space, then I would recommend 
restricting
the value set to single-keyword[1] values only.  That is,
`place-content: end stretch`
means
`align-content: end`
`justify-content: stretch`
(fallback value and `<overflow-position>` can't be specified using the
 shorthand)

Doing something more advanced (parsing eagerly) would be hard to grok 
for humans
and parsers alike. :-)

[1] in this context, `last baseline` counts as one keyword though

-- 
GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/595#issuecomment-257620722 
using your GitHub account
Received on Tuesday, 1 November 2016 16:49:40 UTC

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