W3C home > Mailing lists > Public > www-svg@w3.org > January 2013

Re: Porting fill/stroke (and -opacity variants) to plain CSS

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 23 Jan 2013 15:30:38 -0800
Message-ID: <CAAWBYDCMdQJkkcU4pehM7MrVhF+iFgNxY-USudT-+m0BE6nU8w@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: Dirk Schulze <dschulze@adobe.com>, www-svg <www-svg@w3.org>
On Wed, Jan 23, 2013 at 3:23 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> On 24/01/13 9:36 AM, Dirk Schulze wrote:
>> Here is a blog post about these properties:
>>
>> https://www.webkit.org/blog/85/introducing-text-stroke/
>
>
> Thanks.
>
> That post is not exactly clear about what "not set" means for
> text-fill-color.  Presumably it has an initial value of currentColor.
>
> In SVG at the moment we have these initial values:
>
>   fill: black
>   stroke: none
>   stroke-width: 1px
>
> while these properties are:
>
>   text-fill-color: currentColor
>   text-stroke-color: currentColor
>   text-stroke-width: 0
>
> How do we reconcile these?

As I laid out in my previous email, I think we can get away with
changing the initial value of 'fill' to "currentColor", and then using
a UA style sheet to set it to "black" for SVG elements.

We can just ignore the disconnect in stroke initial values.  Both ways
validly suppress the initial display, and so we can just leave
'stroke' as it is.

~TJ
Received on Wednesday, 23 January 2013 23:31:26 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:54 GMT