W3C home > Mailing lists > Public > www-style@w3.org > July 2015

Re: [css-variables] Behavior of `--foo: var(invalid var function)`

From: Cameron McCormack <cam@mcc.id.au>
Date: Fri, 17 Jul 2015 08:07:51 +1000
Cc: Simon Sapin <simon.sapin@exyr.org>, www-style list <www-style@w3.org>
Message-Id: <BEC1FD95-F248-41AA-9522-64A27FA4F781@mcc.id.au>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

> On 17 Jul 2015, at 4:35 am, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> 
> On Thu, Jul 16, 2015 at 6:33 AM, Simon Sapin <simon.sapin@exyr.org <mailto:simon.sapin@exyr.org>> wrote:
>> But it doesn’t say what to do with var() functions that are *not* valid but
>> still match the property’s value grammar.
>> 
>> I think that Firefox’s behavior is slightly more useful, and Tab said he’s
>> willing to align the spec with it.
> 
> I just talked with Levi, our implementor, and he said that we match
> FF's behavior here, and will throw out #2 as invalid at parse time.
> So I'll just update the spec to match.

Sounds good. This also matches my comments in https://lists.w3.org/Archives/Public/www-style/2013Dec/0148.html <https://lists.w3.org/Archives/Public/www-style/2013Dec/0148.html>.
Received on Thursday, 16 July 2015 22:08:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:18 UTC