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

Re: [css3-fonts] Unclear whether bad ranges are dropped at parse time

From: John Daggett <jdaggett@mozilla.com>
Date: Thu, 6 Jun 2013 00:39:53 -0700 (PDT)
To: www-style@w3.org
Message-ID: <1632889100.20658493.1370504393116.JavaMail.root@mozilla.com>

David Baron wrote:

>   # For interval ranges, the start and end codepoints must be valid
>   # Unicode values and the end codepoint must be greater than or
>   # equal to the start codepoint. 
> 
> which is an authoring conformance requirement, but it never defines
> such a range as invalid, which would in turn invoke the
> implementation conformance requirement earlier:

I somewhat puzzled by why this is classified as an "authoring
conformance requirement" rather than simply part of the definition of
interval range.  I've tweaked this to replace "must" with "is", I
*think* that's what you're getting at.

The logic of that section is that a <urange> has three forms and that
anything that doesn't fit one of the three defined forms is invalid
and so normal invalid value handling rules apply.

Cheers,

John Daggett
Received on Thursday, 6 June 2013 07:40:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:12 UTC