W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2014

[filter-effects] Filter primitive subregions and input clipping

From: Max Vujovic <mvujovic@adobe.com>
Date: Mon, 3 Nov 2014 23:31:15 +0000
To: "public-fx@w3.org" <public-fx@w3.org>
CC: "senorblanco@chromium.org" <senorblanco@chromium.org>, Dirk Schulze <dschulze@adobe.com>
Message-ID: <F74EB6C0-ED4A-490B-AAD6-DDBF97C6F4F6@adobe.com>
Hi folks,

Iím wondering why the spec says that filter primitive subregions clip their input.

Implementations donít do it, and Iím struggling to find a benefit of it. IMO, we should remove this requirement.

I agree with Stephen Whiteís statement last time this was discussed [1]:
"I suppose you could make the argument that if you had only output clipping, you could always achieve input-and-output clipping by inserting a no-op node (e.g., FEOffset) with the filter primitive subregion set to the same values as the child node, e.g.  http://jsfiddle.net/C6zSD/3/. Whereas if you have input-and-input clipping, there's no easy way to achieve output clipping only."

According to my tests (posted on a related spec bug [2]):
- Safari, Firefox, and Chrome do not clip the input to a filter primitive to its primitive subregion. IE11 was inconclusive; I think I ran into a different bug.
- Safari, Firefox, IE11, and Chrome all clip the input to a filter to its filter region.

Thoughts?

Thanks!
Max

[1]: http://lists.w3.org/Archives/Public/public-fx/2013JulSep/0082.html
[2]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26432
Received on Monday, 3 November 2014 23:31:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 03:33:53 UTC