Re: [paint] Publishing FPWD of Fill and Stroke Module

I'm not sure that would be web-compatible.  It breaks any case where `fill`
is set with the expectation that it would inherit into inline SVG.  Unless
you really meant only "svg:root" elements, in which case all my original
concerns still apply to inline SVG.

Either way, I'd still recommend adding an issue to the spec, to look into
the compat issues.

And of course, for any version that requires new user-agent stylesheet
rules, we'll need a section of the spec for that.  (I assume this is the
part you were "planning to do"!)


On 16 March 2017 at 11:47, Tab Atkins Jr. <> wrote:

> On Thu, Mar 16, 2017 at 10:12 AM, Amelia Bellamy-Royds
> <> wrote:
> > The initial value of fill-color isn't backwards compatible.  It needs to
> be
> > "black" to be compatible with the initial value of SVG fill.  But then
> that
> > isn't backwards-compatible with regular CSS text rendering (which uses
> > color).
> >
> > Options:
> >
> > give fill-color an `auto` value which equates to `black` for SVG elements
> > and to `currentColor` elsewhere.
> >
> > add a separate text-rendering-mode property that determines whether to
> use
> > basic text rendering (currentColor fill, stroke ignored) vs fill+stroke
> > paint (and use the user stylesheet to switch mode for <svg> then switch
> it
> > back for <foreignObject>).
> We went for a third option (which we were planning to do, but forgot
> to put in the spec): set fill-color to black for root svg elements in
> the UA stylesheet.
> ~TJ and fantasai

Received on Thursday, 16 March 2017 18:10:09 UTC