Re: Margins for filters?

> Specifically, I suggest we change the definition of the filter effects
> region so that we no longer clip to it. The filter effects region
> becomes completely irrelevant and we can remove it. I suggest we
> continue to allow filter primitive subregions to clip filter
> primitives, but that we make the default filter primitive subregion
> (for all filter primitives) be infinite so no clipping is performed.
> Remove all mention of "intermediate offscreens".
I would like to keep filter effect regions to be consistent with masking
or pattern. The most users know that they clip the results. But they
should just clip the end result of the primitive calculations. So that
you can move primitives forward and backward by feOffset without the
fear that they get clipped by the filter effect region during the
calculation.

> We could redefine 'filterRes' to specify the maximum size of the
> implementation's temporary buffers, but it's probably better to drop
> it from the spec entirely. I don't think authors can pick a specific
> filterRes that will be optimal across a wide variety of devices and
> implementations.
I agree. It's difficult to specify 'filterRes', if you don't know how
the viewer optimize the effects. This may also depend on the platform
(smart phone <> desktop).

Received on Sunday, 18 April 2010 20:04:31 UTC