On Fri, 8 Apr 2011, Tab Atkins Jr. wrote:
In the legacy color parsing algorithm
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#rules-for-parsing-a-legacy-color-value,
steps 5 and 6 concern CSS color names - 'transparent' should raise an
error, and
On Fri, Jul 15, 2011 at 11:43 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 8 Apr 2011, Tab Atkins Jr. wrote:
In the legacy color parsing algorithm
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#rules-for-parsing-a-legacy-color-value,
steps 5 and 6 concern
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
On Fri, Jul 15, 2011 at 11:57 AM, L. David Baron dba...@dbaron.org 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
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
On Fri, Jul 15, 2011 at 1:18 PM, Ian Hickson i...@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
On Fri, Apr 8, 2011 at 10:26 PM, Boris Zbarsky bzbar...@mit.edu 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
In the legacy color parsing algorithm
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#rules-for-parsing-a-legacy-color-value,
steps 5 and 6 concern CSS color names - 'transparent' should raise an
error, and color names should be respected. All other CSS color
On 4/8/11 1:54 PM, Tab Atkins Jr. wrote:
In the legacy color parsing algorithm
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#rules-for-parsing-a-legacy-color-value,
steps 5 and 6 concern CSS color names - 'transparent' should raise an
error, and color
On Fri, Apr 8, 2011 at 2:26 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 4/8/11 1:54 PM, Tab Atkins Jr. wrote:
In the legacy color parsing algorithm
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#rules-for-parsing-a-legacy-color-value,
steps 5 and 6
10 matches
Mail list logo