I just wanted to point out that the problem described for text-shadow can be
a lot more complicated than animating 4 different values, e.g.:
text-shadow: 1px 1px 3px #666, -1px -1px 3px #FFF, 1px 1px #666, -1px -1px
#FFF;
So here you have 14 values.
Also, box-shadow was removed from the CSS3 spe
dotnetCarpenter wrote:
> ...
> It's actually fun to think that even thought IE rightly deserve a lot
> bashing for stopping browser innovation, it was the first browser to
> support image transparency, persistent storage, gradient ect. haha!
>
^_^ And then you look at what they did in ie8 to all
Wouldn't it be fair to put this under "edge cases"?
When you have a CSS property that has not been implemented in a pattern
similar to other long-standing properties (e.g. text-shadow-radius), it
seems that animating such a combined property would fall under an edge case
requiring custom code.
IM
