- From: David Hyatt <hyatt@apple.com>
- Date: Fri, 04 Mar 2011 16:47:22 -0600
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Sylvain Galineau <sylvaing@microsoft.com>, fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Let's just make color a required component of shadows and not allow it to be omitted. Then we dodge the whole issue. :) dave (hyatt@apple.com) On Mar 3, 2011, at 6:31 PM, Tab Atkins Jr. wrote: > On Thu, Mar 3, 2011 at 4:25 PM, Sylvain Galineau <sylvaing@microsoft.com> wrote: >> [fantasai:] >>> Ok, if we have interop on currentColor, we can update the spec that way. >>> I'm kindof surprised, because if you do that for text-shadows, it's really >>> almost never the right color. >> >> For text-shadow, I can understand how it's a weird default but that is also >> the interop behavior today. There might be a better default - would something >> half way between foreground and background colors work better ? - but the >> interop and <shadow> consistency are already there. I also expect authors to >> want to pick their shadow colors carefully so I don't think it will be a burden >> in practice. It really is a testability/interop nitpick more than anything else. > > I know that I've never written a text-shadow without an explicit > color, and have never seen one in the wild without a color either. > They may exist, but I believe they're very minority. We don't really > have to worry about it. > > ~TJ >
Received on Friday, 4 March 2011 22:48:36 UTC