W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2013

Re: [filter-effects] resolution dependent filter primitives

From: Dirk Schulze <dschulze@adobe.com>
Date: Tue, 27 Aug 2013 10:39:12 -0700
To: Michael Mullany <michael@sencha.com>
CC: Jasper van de Gronde <th.v.d.gronde@hccnet.nl>, "www-svg@w3.org" <www-svg@w3.org>, "public-fx@w3.org" <public-fx@w3.org>
Message-ID: <DDB88152-2326-4D99-A7DA-AD37C3333D42@adobe.com>

On Aug 27, 2013, at 7:22 PM, Michael Mullany <michael@sencha.com> wrote:

> 
> 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).

Means there is no better time to talk about removing features that just do a little good and discuss alternatives that are better.

Greetings,
Dirk
Received on Tuesday, 27 August 2013 17:39:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:46 UTC