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

Re: [filter-effects] color-interpolation-filters

From: Tavmjong Bah <tav.w3c@gmail.com>
Date: Wed, 9 Jan 2013 10:33:12 +0100
Message-ID: <CAHfwxgq8BcsfSA54tyfwh=4vH1PffNZ4U6gJTh4XjHhS2uYVoQ@mail.gmail.com>
To: Robert Longson <longsonr@gmail.com>
Cc: "www-svg@w3.org" <www-svg@w3.org>
I am not sure this is the correct thing to do. It is better, I think, to
have consistency between the four "source" like filters and the spec for
feTurbulence states:

"The generated color and alpha values are in the color space determined by
the value of property

As the default color space for filters is linearRGB. It would seem a bit
strange to not be able to define colors in linearRGB (in particular, the
lighting filters). If you want the colors to be defined in sRGB, you can
set 'color-interpolation-filters' to 'sRGB',

On Wed, Jan 9, 2013 at 12:17 AM, Robert Longson <longsonr@gmail.com> wrote:

> > I assumed that feFlood would be like feTurbulence in that the values are
> defined in the color space of the filter primitive. This is what Webkit is
> doing now... but not Firefox and Opera (or Batik) which assume sRGB.
> Whatever is done for feFlood should be also done for  feSpecularLighting
> and feDiffuseLighting. For feDiffuseLighting, both Firefox and Chrome use
> the color space of the filter primitive while Opera assumes sRGB. There is
> no consistency at all for feSpecularLighting.
> I'll raise a bug for Firefox to change feSpecular and
> feDiffuseLighting to be sRGB.
> Robert
Received on Wednesday, 9 January 2013 09:33:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:40 UTC