W3C home > Mailing lists > Public > www-style@w3.org > November 2014

Re: [css-syntax] Removed <unicode-range-token>, please review

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 14 Nov 2014 11:20:26 -0800
Message-ID: <CAAWBYDCuyVi6ZcYmM1AoPSJ4hyvrrUrrfSqAm2=g8WoC5CUB=Q@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: www-style list <www-style@w3.org>
On Thu, Nov 13, 2014 at 9:03 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Thu, Nov 13, 2014 at 7:42 PM, John Daggett <jdaggett@mozilla.com> wrote:
>> Tab Atkins wrote:
>>> In section 7.1:
>>>
>>> To determine what codepoints the <urange> represents:
>>>
>>> 1. If end value is greater than the maximum allowed code point, set
>>>    it to the maximum allowed code point.
>>
>> No, this is invalid syntax and the descriptor defintion should be rejected.
>>
>>> 2. If start value is greater than end value, the <urange>
>>>    represents an empty range of codepoints.
>>
>> Ditto. Plus you introduce serialization problems by allowing "empty
>> range". I went through this with the Fonts spec, that's why it isn't
>> defined this way. :)
>
> Sure, I can just make those both invalid <urange> rather than empty or
> truncated.  Not a problem.

And done.  Now those errors make the <urange> invalid and a syntax
error, rather than triggering error-correction.

~TJ
Received on Friday, 14 November 2014 19:21:14 UTC

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