[go: up one dir, main page]

Re: [css3-values] new editor's draft (and [css3-box])

Christoph Päper wrote:

First, thanks for your review. Very helpful. An updated draft can be
found here:

  http://dev.w3.org/csswg/css3-values/

 > >   - the 'gd' unit has been added
 > 
 > I assume you mean 'gr'

Yes.

 > as 'gd' only appears twice in the draft and  
 > without definition.

Fixed. (Sections that are commented out in the source document is
sometimes put back in by the processor)

 > Please add to the table in section 3.3.2 Absolute length units:
 > 
 >    um   micrometers (µm); 1um is equal to 1/1000 millimeter.
 >    dd   didot; 1dd is equal to 3/8 millimeter.
 >    cc   cicero; 1cc is equal to 12 didots.
 >    q    kyu; 1q is equal to 1/4 millimeter.
 > 
 > Although not many a designer uses these (yet or still), they should  
 > be reasonably cheap to implement.

Cheap to implement, yes. But it will be a painful transition period
when some browsers support them and others don't. Do we really nee
these? When would you use um? Who uses dd on anything
computer-related? And kyu?

 > Please add, with much less emphasis, to section 3.3.3 Relative length  
 > units:
 > 
 >    ln   the line height of the element (or the parent element's line  
 > height if set on the ‘line-height’ property)

Use case?

 >    pel  device pixel

Use case?

 > Remove the phrase "are used with aural cascading style sheets" from  
 > 3.3.7 Angles, 3.3.8 Times and 3.3.9 Frequencies, because those units  
 > may (and will) be used by other parts of CSS, e.g. Transitions and  
 > Animations. Let Modules limit the range or specify the clipping of  
 > units, like angles in aural CSS.

Agreed, done.

 > Do angles need minutes ('min') and seconds (maybe 'sec' in opposition  
 > to temporal 's'), do times need minutes more?

As in one degree is equal to 60 minutes, and one minute is equal to 60 seconds?

I think it would be easy to confuse times and angles if minutes and
seconds are use to measure both, and I don't see a compelling use
case.

 > Change the MAY to a SHOULD requirement in 3.5.2 The ‘url’ function:

Done.

 > | The URI may be quoted with single quote (') or double quote (")
 > | characters.
 > 
 > The same should be done to font families.

The draft says: 

  Font family names are like strings

And: 

  Strings can either be written with double quotes or with single
  quotes.

So, I think it's clear tha both single and double quotes can be used.

 > | Parentheses, commas, whitespace characters, single quotes (') and
 > | double quotes (") appearing in a URI must be escaped with a
 > | backslash:
 > 
 > If I remember the RFCs correctly, of these only commas and perhaps  
 > parentheses may appear in URIs. (I'm not sure about fragment  
 > identifiers, though.)

Anyone else knows?

 > Drop the first occurence of 'RGB' in 3.6.2 Colors, there's HSL and  
 > perhaps more in the future.

Indeed. Done.

Cheers,

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome

Received on Monday, 19 January 2009 17:41:47 UTC