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

2011-07-15 Thread Tab Atkins Jr.
On Fri, Jul 15, 2011 at 1:18 PM, Ian Hickson 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, does

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

2011-07-15 Thread Ian Hickson
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

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

2011-07-15 Thread Tab Atkins Jr.
On Fri, Jul 15, 2011 at 11:57 AM, L. David Baron wrote: > On Friday 2011-04-08 13:54 -0700, Tab Atkins Jr. wrote: >> This doesn't match Webkit's behavior.  Instead of steps 5 and 6, we >> just try to parse it as a CSS color. > > As I pointed out in > http://lists.whatwg.org/pipermail/whatwg-whatwg

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

2011-07-15 Thread L. David Baron
On Friday 2011-04-08 13:54 -0700, Tab Atkins Jr. wrote: > This doesn't match Webkit's behavior. Instead of steps 5 and 6, we > just try to parse it as a CSS color. As I pointed out in http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-May/026449.html this isn't compatible with doing the fol

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

2011-07-15 Thread Tab Atkins Jr.
On Fri, Jul 15, 2011 at 11:43 AM, Ian Hickson wrote: > On Fri, 8 Apr 2011, Tab Atkins Jr. wrote: >> In the legacy color parsing algorithm >> , >> steps 5 and 6 concern CSS

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

2011-07-15 Thread Ian Hickson
On Fri, 8 Apr 2011, Tab Atkins Jr. wrote: > > In the legacy color parsing algorithm > , > > steps 5 and 6 concern CSS color names - 'transparent' should raise an > error

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

2011-04-13 Thread Philip Taylor
On Fri, Apr 8, 2011 at 10:26 PM, Boris Zbarsky wrote: > On 4/8/11 1:54 PM, Tab Atkins Jr. wrote: >> >> In the legacy color parsing algorithm [...] >> Could we change those two steps to just say "If keyword is a valid CSS >> color value, then return the simple color corresponding to that >> value."

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

2011-04-08 Thread Tab Atkins Jr.
On Fri, Apr 8, 2011 at 2:26 PM, Boris Zbarsky wrote: > On 4/8/11 1:54 PM, Tab Atkins Jr. wrote: >> >> In the legacy color parsing algorithm >> >> , >> steps 5 and 6 concern

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

2011-04-08 Thread Boris Zbarsky
On 4/8/11 1:54 PM, Tab Atkins Jr. wrote: In the legacy color parsing algorithm , steps 5 and 6 concern CSS color names - 'transparent' should raise an error, and color nam

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

2011-04-08 Thread Tab Atkins Jr.
In the legacy color parsing algorithm , steps 5 and 6 concern CSS color names - 'transparent' should raise an error, and color names should be respected. All other CSS colo