Re: [filter-effects] resolution dependent filter primitives

>
>
> Well, scaling of the whole filter chain or a single primitive was
> specified for 13 years. And yet I can't find any usage in the web beside
> tests of browser vendors. Again, it is extremely hard to determine the
> right scale level for the horizontal and vertical axis and chances are high
> that it does not work as expected on a different object. I assume that this
> is the reason why it actually was never used by authors. Implementations on
> the other hand already have these information. At the end both alternatives
> are reasonable for me. Giving the author a theoretically powerful but
> practical fragile tool like kernelUnitLength doesn't help IMO.
>
>
Well please remember that filter usage in general has been minimal because
filters haven't been available cross platform until IE10 and Safari 6 (aka
the last year). On Android browsers, they're still only available on
Android 4 on the latest Samsung browsers. There have also been showstopper
bugs on each browser (not to mention that light source positions are still
not correct in Chrome and document fragments are still not supported as
inputs on Firefox).