- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 7 Nov 2012 07:53:00 -0800
- To: Dirk Schulze <dschulze@adobe.com>
- Cc: "public-fx@w3.org" <public-fx@w3.org>, "robert@ocallahan.org" <robert@ocallahan.org>, Robert Longson <longsonr@gmail.com>
On Wed, Nov 7, 2012 at 7:22 AM, Dirk Schulze <dschulze@adobe.com> wrote: > SVG Filters had some so called pseudo filter primitives (SourceGraphic, SourceAlpha, BackgroundImage, BackgroundAlpha, FillPaint, StrokePaint). We have two issues in the spec to this topic. What should we do with FillPaint and StrokePaint on HTML elements? > > Short explanation: > FillPaint: This keyword represents the value of the ‘fill’ property on the target element for the filter effect. > StrokePaint: This keyword represents the value of the ‘stroke’ property on the target element for the filter effect. > > 'fill' and 'stroke' currently just apply to SVG shapes and text content elements. This does not include HTML elements. This is why Filter Effects currently suggest taking transparent black on HTML elements for these keywords. However, Firefox still uses the values of these properties, independent if the element is an HTML or SVG element. > > I would be in favor for relaxing the restriction and follow Firefox. I am not sure if that necessarily means that 'fill' and 'stroke' apply to all elements in the future. That might need to be discussed in an FXTF call. If there are no objections, I will go ahead and do the changes. I'm not opposed to this. Even though 'fill' and 'stroke' don't do anything on non-SVG elements, their values are still well-defined, so might as well be simple if there's no compat impact. Firefox suggests there isn't. ~TJ
Received on Wednesday, 7 November 2012 15:53:50 UTC