W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: [css-shapes] basic shape syntax in prose

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 27 Sep 2013 15:07:34 -0700
Message-ID: <CAAWBYDC2kepi4-9Oe=rJ3YcvzypqWupkBnFdMzTwm6w=6O06mg@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: Dirk Schulze <dschulze@adobe.com>, "www-style@w3.org" <www-style@w3.org>
On Fri, Sep 27, 2013 at 1:54 PM, Alan Stearns <stearns@adobe.com> wrote:
> On 9/27/13 1:19 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>>On Fri, Sep 27, 2013 at 1:06 PM, Alan Stearns <stearns@adobe.com> wrote:
>>> The normative grammar-based definition is not readable when precise, and
>>> not precise when readable. I think there's a false sense of accuracy in
>>> the format for functional notation, as we seem to be willing to fudge
>>> whitespace rules everywhere.
>>
>>What do you mean?
>
> This definition doesn't precisely define what's actually allowed in hsl():
>
> hsl() = hsl( <hue>, <percentage>, <percentage> )
>
> It's actually something more like:
>
> hsl() = hsl([ ]*<hue>[ ]*,[ ]*<percentage>[ ]*,[ ]*<percentage>[ ]*)

That's not being loose - the definition of the grammar explicitly says
that whitespace is allowed between any tokens.
<http://dev.w3.org/csswg/css-values/#component-whitespace>

> -inspired is the key. CSSWG additions and conventions are what trip people
> up.

They're still documented, and unambiguous, unlike prose.

~TJ
Received on Friday, 27 September 2013 22:08:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC