W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2011

Re: Filter Clipping Region

From: Dirk Schulze <vbs85@gmx.de>
Date: Tue, 11 Jan 2011 18:29:34 +0100
Cc: "Erik Dahlstrom" <ed@opera.com>, public-fx@w3.org
Message-Id: <835795EF-5FFF-4BC1-B4F4-71F3320A3D57@gmx.de>
To: Brad Kemper <brad.kemper@gmail.com>

Am 11.01.2011 um 18:07 schrieb Brad Kemper:

> 
> On Jan 11, 2011, at 7:55 AM, Erik Dahlstrom wrote:
> 
>>> On the other hand, this implementation still cause the long known confusions for web developer. In many cases the shadow will be clipped because of the hard clipping region of (-10%, -10%, 120%, 120%) of the boundingBox of the target.
>> 
>> That's a separate issue, it affects all filter primitives (even if blur is the most common example). I think the svg filters should probably default to not clipping instead, e.g by introducing some sort of auto region calculation.
> 
> Yes, please. I find the "Filter Region Extensions" [1] to be wholly confusing. It seems to me that clipping the input could be useful, but what effect requires clipping the output region to anything less than what the filter produces? Are there effects that will spread to the whole canvas or viewport otherwise?
Yes, for example Lightning effects might affect an infinite big area if you don't define a clipping area. The same can happen for feComposite in combination with the operator arithmetic. So auto sizing is a great idea, and most implementations use it internally already. But there are situations where the area can't be determined.

Cheers
Dirk
Received on Tuesday, 11 January 2011 17:30:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 17:30:10 GMT