[whatwg] Accept full CSS colors in the legacy color parsing algorithm

Tab Atkins Jr. jackalmage at gmail.com
Fri Jul 15 14:09:15 PDT 2011

On Fri, Jul 15, 2011 at 1:18 PM, Ian Hickson <ian at hixie.ch> wrote:
> On Fri, 15 Jul 2011, Tab Atkins Jr. wrote:
>> I'll note, though, that the spec algorithm seems to be Firefox's
>> behavior, which differs in a few significant points from IE's.  In
>> particular, IE doesn't strip whitespace from the color, doesn't have the
>> same "truncate at 128 bytes" behavior, and doesn't recognize a 3-digit
>> hex color as a CSS color (instead parsing it with legacy rules).
>> I doubt it matters too much, but was there any particular reason you
>> went with Firefox over IE here?
> See:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=9847
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12372
> Basically, it looks like IE does strip whitespace in some cases, the main
> difference is that it doesn't handle #123 the same as #112233. Since that
> would introduce an incompatibility with CSS, and since there was no
> interop on that case, I figured (based on input from Aryeh and dbaron) we
> might as well go with the sane behaviour.
> Interop isn't perfect here so there's not really any winning whatever we do.

That's fine.  I was just curious.  Like I said, WebKit now matches the
spec, so whatever.


More information about the whatwg mailing list