Re: [css3-conditional] Supported vs. valid declaration. from L. David Baron on 2012-09-20 (www-style@w3.org from September 2012)

From: L. David Baron <dbaron@dbaron.org>
Date: Thu, 20 Sep 2012 12:48:51 -0700
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, www-style@w3.org
Message-ID: <20120920194851.GB9694@crum.dbaron.org>

On Thursday 2012-09-20 14:51 +0200, Simon Sapin wrote:
> Le 20/09/2012 14:40, Boris Zbarsky a écrit :
> >>I’m thinking in particular of 6.2’s comment on values that might be
> >>valid in a spec but the UA "do not have a usable level of support for".
> >Sane UAs would treat that as "invalid".  Of course historically not all
> >UAs are always sane.:(
> 
> §6.2 seems to require such sanity in @supports for conformance, but
> it (or something) should do the same with declarations.

The second sentence of section 6.2 [1] was intended to do exactly
this, where it says:

  # must not accept or support a declaration containing such a value

Would it be clearer to change:
  accept -> accept as a declaration
  support -> <a href="#support-definition">support</a>
?

Or do you see another way to make it clearer?

-David

[1] http://dev.w3.org/csswg/css3-conditional/#partial-implementations

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂

Received on Thursday, 20 September 2012 19:49:18 UTC