917766 - Filter not applied to tspan with svg.text.css-frames.enabled

Status: RESOLVED INVALID

(Core :: SVG, defect)

Comment 1

[Robert Longson [:longsonr]]

The black X should cover (and therefore hide) the red X in the ietestcenter test.

Comment 2

[Cameron McCormack (:heycam)]

You are right that this used to work, but the spec doesn't call for it.  http://www.w3.org/TR/SVG11/filters.html#FilterProperty says that 'filter' applies to container elements and graphics elements, but <tspan> is neither.  (Although an <a> element is a container element, so you could technically get around the restriction by wrapping the <tspan> in an <a>.)

Comment 3

[Robert Longson [:longsonr]]

Invalid then.

Comment 4

[Cameron McCormack (:heycam)]

Though I should point out that Chrome does support this.  Maybe something to bring up in the WG first.

Comment 5

[Robert Longson [:longsonr]]

If the specification was changed would we find it easy to implement?

Comment 6

[Cameron McCormack (:heycam)]

I had a look today. It won't be simple because we can't just call nsSVGUtils::PaintFrameWithEffects as we're dealing with rendered runs. We'd need to get the TextRenderedRunIterator to keep a stack of the frames it's traversed into and then do the stuff that PaintFrameWithEffects does.

Comment 7

[Robert Longson [:longsonr]]

That's what I thought. 

Also, if filter changed in the specification then I don't see why clip-path and mask shouldn't change too. I expect we used to support both of these on <tspan> too but we no longer do.