@tabatkins could you review, and confirm && was a mistake?

For what it's worth, this syntax was introduced many years ago in 7bb4fba?diff=unified#diff-f80d8fc0ac03564f1ec01e8503aeb5bea39694d9b20764727225b00510671de3R2249, initially restricted to <cap-linear-color-stop>. Later on it was relaxed to apply to any <linear-color-stop> in 321c3e5#diff-6558f7be1858e8498722b9ac5981271f70d5219829f557f54fa720cf443c3e5bR1681.

Sebastian

Also for what it is worth, Chrome and FF do not parse position(s) before the color as valid, and if it should be allowed, it may be odd to be able to specify both positions before or after the color, but not a color between them.

Yeah, reviewing the diff I'm almost certain it was just a mistake while writing it - it looked reasonable to use an && in the grammar while I was rewriting. I still think it's probably reasonable to do so, but nobody's followed that in forever and it's not very important, so reverting to the old spec text which matches impls makes sense.