[Bug 26432] Specify that filter regions clip input

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26432

--- Comment #4 from Max Vujovic <mvujovic@adobe.com> ---
(In reply to Dirk Schulze from comment #3)
> Do you disagree?

I agree. If the filter primitive subregion clips input and intermediate
offscreens cannot exceed the filter region, I believe that's the same as saying
the filter region clips the input.

IIRC, no browsers actually use the filter primitive subregion to clip a
previous filter primitive's input. They only use it to clip a filter
primitive's output.

However, I believe all browsers use the filter region to clip input. (I will
attach a better test case shortly.)

To match all the implementations, I'd change the spec to say filter primitive
subregions clip their primitive's output, and filter regions clip the input
SourceGraphic (or other input).

I don't see any harm in primitive subregions not clipping input. You can
achieve the same result by inserting an extra no-op primitive of some kind with
a primitive subregion if you really want to clip both input and output.

This is probably a separate bug, though. The current spec language does work
for filter regions clipping input via filter primitive subregion input
clipping.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 3 November 2014 22:12:34 UTC