Re: Typos and such

On 09/19/2010 12:49 AM, Lobotom Dysmon wrote:
> About *CSS Backgrounds and Borders Module Level 3* - *Working Draft 12 June 2010*
>
> Hi,

Hi! I'm sorry I missed your comments. Replies below.

(In the future, if you add the subject code requested in the Status
section of the spec, it's less likely your comments will get lost.)

> - in 4.4. The ‘border-radius’ properties
> Prose specifies the meaning of border-radius values for the case of values
> being given before and after the slash, and for the case of no slash being used.
> I believe it makes quite unclear what behavior is induced when a slash is used
> but followed by no value: wether this is illegal syntax, or as for
> border-*-radius the second value is copied from the first.

The syntax of a property, in general, is given in the property definition
table. Occasionally, it may be supplemented by additional restrictions in
the prose, if the restriction is difficult to represent in the grammar,
but in this case the restriction you're looking for is in the grammar of
the property value definition:

   [ <length> | <percentage> ]{1,4} [ / [ <length> | <percentage> ]{1,4} ]?

The slash and the second [<length>|<percentage>] set are required to appear
together, if they appear at all.

> - 4.4.4. Overlapping Curves
> In Example XXII a line goes like this: "/The height (2.5em) is enough for the
> specified radii (0.5em plus *2.5em*)./" My math and more importantly the rest
> of the example clearly states height (2.5 em) is equal to 0.5em plus 2.0em
> (not 2.5em).
>
> - In Example XXIV
> ".../is equivalent to the set of four rules shown after it/:" is followed by
> a list of _five_ rules.

Fixed. Will appear in the next publication. :)

> - 5.5. The ‘border-image-repeat’ property
> In the summary box, 'space' is not listed as a possible value for the property.
>
> - Example XXIX
> A simple type, introduction line for the example reads :
> "/Below are some examples of an orange box with a blue border being *being* given a drop shadow."
> ...One "being/" to many

Also fixed.

> Hoping this brings more benefit than trouble.

Thanks for taking the trouble to comment. I apologize for not catching your
email sooner.

~fantasai

Received on Monday, 7 March 2011 17:15:30 UTC