[css-variables] editorial nits/suggestions

In section 2:

> Unlike other CSS properties, custom properties are case-sensitive.

I think you want to say "custom property names are case-sensitive",
since the values of these properties remain case-insensitive as per
general CSS property values.

In this section, the first example is an example of a rare syntax
error.  Better to show a simple example of variable definition first
and show the syntax error later on.

After Example 1 is text that reads:

  The <value> in its grammar corresponds to the "value" production in
  CSS 2.1 Chapter 4.1 [CSS21], while <CDO> and <CDC> correspond to the
  tokens of the same name from the same chapter (they represent HTML
  comments showing up in CSS text - "<!--" and "").

Looks like you need to escape something, the last "" should be "-->", right?

Example 6 begins with "{.invalid-example}".  Authoring turd?

In section 3, variable use and the fallback parameter are introduced
but the first example is again a weird syntax error.  Better to have a
simple example illustrating a basic use case (e.g. color use across
multiple elements).  Then another simple example showing how the
fallback parameter works, for example:

  :root {
    var-grad: tabs-amazing-gradient(to bottom right, orange, white);
  }
  background: var(grad, linear-gradient(to bottom right, orange, white));

After these examples of practical use, then get into the "bad syntax"
examples.

> Acknowledgments == <empty>

I think it would be nice to acknowledge all those who tried and
struggled to define a CSS variables feature in the past, since this effort
is a synthesis and/or reaction to those efforts.  Also, to acknowledge the
influences that led to the current proposal (e.g. HTML5 data- attributes?),
along with anyone that chimed in with interesting ideas or counterproposals.
And don't forget to thank your mother, she made it all possible. ;)

Regards,

John Daggett

Received on Wednesday, 27 February 2013 04:06:30 UTC