W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2014

Re: [whatwg] brand-color meta extension

From: Mathias Bynens <mathiasb@opera.com>
Date: Thu, 26 Jun 2014 22:43:07 +0200
Message-Id: <382BB4A0-87E3-454E-BDD6-A6A708F2E195@opera.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>
On 26 Jun 2014, at 22:37, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> On Thu, Jun 26, 2014 at 1:33 PM, Mathias Bynens <mathiasb@opera.com> wrote:
>> On 26 Jun 2014, at 22:24, Mathias Bynens <mathiasb@opera.com> wrote:
>> 
>>> Interesting to see this would be only the second HTML attribute value to get parsed as a simple color (http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#simple-color) rather than a legacy color (the other one being `<input type=color value=foo>`).
>> 
>> Actually, the way it’s currently specced it wouldn’t be a parsed as a simple color value nor as a legacy color value. It should probably be one or the other (rather than introducing a third, new way to parse color values). https://github.com/whatwg/meta-brand-color/issues/1
> 
> Well, the third way is "as CSS", which already exists in the platform.

Parsing a legacy color value is also “as CSS”, with some extra fallback logic in case that fails (which is currently undefined in the `brand-color` spec), and this logic is already used for the majority of HTML attributes that represent a color value.
Received on Thursday, 26 June 2014 20:43:34 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:21 UTC