- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Apr 2022 20:57:35 +0000
- To: public-css-archive@w3.org
> > ``` > > * Is it ok to allow different orders in the syntaxes? > > ``` > > I used the [double pipe](https://drafts.csswg.org/css-values-4/#comb-any) in the syntaxes, i.e. `<color> || <1d-image>`. This allows the two values to be in any order. > > That allows to specify something like `border-color: red stripes(white, silver) stripes(white, silver) yellow lime stripes(black, gray) blue;`. > > We might use juxtaposing instead, i.e. `<color> <1d-image>` to force the order of first `<color>` then `<1d-image>`. Oh no, you need to use a single pipe: `[ <<color>> | <<1d-image>> ]`. It's a `<color>` OR `<1d-image>` but not both. It doesn't make sense to have `border-color: red stripes(white, silver) stripes(white, silver) yellow lime stripes(black, gray) blue;` because you can't tell what is for what side. > > ``` > > * What to do with `<flex>`? > > ``` > > As noted in a [previous comment](https://github.com/w3c/csswg-drafts/pull/7029#issuecomment-1068988402), I reused `<flex>` from CSS Grid 1 because I agree with you that it fits very well this use case. > > Though, as it is now used in two completely different places, should it's description be generalized and be moved somewhere else? And if so, should that be done in this PR already? Yeah, it should go to css-values. @fantasai @tabatkins ? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/7029#issuecomment-1104449356 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 April 2022 20:57:37 UTC