Re: box-shadow bugs

indeed, the new code does accept inset in first or last position and doesnt 
mix up the output! thank you alot.
but some testing showed, that the new code doesnt like three values. only 
two or four px values are accepted:

#first{ box-shadow: 5px 0px rgba(0,0,0,.1); }
#second{ box-shadow: 5px 0px rgba(0,0,0,.1) inset; }
#third{ box-shadow: inset 5px 0px rgba(0,0,0,0.1); }
#fourth{ box-shadow: 5px 5px 5px rgb(0,0,0); }
#fifth{ box-shadow: 5px 5px 5px 5px rgb(0,0,0); }

#fourth is thrown as an error!? i guess this is incorrect.

Andreas


----- Original Message ----- 
From: "Yves Lafon" <ylafon@w3.org>
To: "Andreas Riddering" <Andreas.Riddering@t-online.de>
Cc: "Brian Todd" <DarthKitty10@yahoo.com>; <www-validator-css@w3.org>
Sent: Wednesday, April 04, 2012 9:46 PM
Subject: Re: box-shadow bugs


On Wed, 4 Apr 2012, Andreas Riddering wrote:

> So why does the validator only accept those box-shadows, if the inset 
> comes first?

Because the implementation was using the definition of a very old
specification (2005).
The new code (on http://qa-dev.w3.org:8001/css-validator/ ) is not yet
moved in production as a big change was made in another part and needs
extra testing.

> ----- Original Message ----- From: "Yves Lafon" <ylafon@w3.org>
>
> No, "inset" can be first or last.
>> From http://www.w3.org/TR/2011/REC-CSS2-20110607/about.html#value-defs
> <<
> A double ampersand (&&) separates two or more components, all of which
> must occur, in any order.
>>>
>
>
>

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves

Received on Thursday, 5 April 2012 07:38:12 UTC