W3C home > Mailing lists > Public > www-style@w3.org > February 2017

Re: [css-variables] testsuite status and interoperability

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 21 Feb 2017 09:59:34 -0800
Message-ID: <CAAWBYDDR4XVcJZ3r22PuSPWruaUSbZu1kj0ED5di-r4S6ew2KQ@mail.gmail.com>
To: Chris Lilley <chris@w3.org>
Cc: www-style list <www-style@w3.org>, Geoffrey Sneddon <me@gsnedders.com>
On Sat, Feb 18, 2017 at 3:19 PM, Chris Lilley <chris@w3.org> wrote:
> On 2017-02-17 18:18, Tab Atkins Jr. wrote:
>> On Fri, Feb 17, 2017 at 2:39 PM, Chris Lilley <chris@w3.org> wrote:
>>>
>>> The only testable  thing about serialization in css-variables is
>>>
>>> Custom property names must be serialized with the casing as provided by
>>> the
>>> author.
>>>
>>>
>>> and then goes on to kind of contradict itself by saying that
>>> implementations
>>> typically don't do that.
>>>
>>> Ordinarily, property names are restricted to the ASCII range and are
>>> ASCII
>>> case-insensitive, so implementations typically serialize the name
>>> lowercased.
>>
>> This isn't contradicting itself, it's referring to the "ordinary"
>> behavior for non-custom properties.
>
> Ah, okay. In that case the spec text could be clarified. Perhaps
> s/Ordinarily, property names/Ordinarily, non-custom property names/

Sounds fine to me.  Done.  (In both places where I use this construction. ^_^)

~TJ
Received on Tuesday, 21 February 2017 18:00:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 February 2017 18:00:31 UTC