- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Aug 2022 14:53:32 +0000
- To: public-css-archive@w3.org
I think the discussion the working group had related to the `|` combinator, which accepts exactly one of the alternatives. I don't think it's relevant to the `&&` combinator or to the all-values-present case of the `||` combinator (since these combinators are [not dependent on order of the grammar](https://drafts.csswg.org/css-values-4/#component-combinators), from which you can infer that the parse-time handling of them is not greedy). Or, to put it another way, when parsing `<length> && <number>` or `<length> || <number>` none of the values `0 1`, `1px 0`, `0 1px`, or `1 0` is ambiguous. The first two have the `<length>` before the `<number>`, and the latter two have the `<number>` before the `<length>`. However, the cases that are ambiguous, and thus affected by the resolution above, are parsing `0` as `<length> | <number>` or as `<length> || <number>`; the resolution above says it is parsed as a `<number>`. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/489#issuecomment-1216750258 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 August 2022 14:53:34 UTC