Markus, Tobias, and Tantek will update the wiki page with our proposed normative text.
Our key use case here is Shumway, where graphics filter implementations in JS code have not (yet) been able to offer acceptable performance characteristics in Canvas2D. We've proven that it's polyfillable in other browsers, though with the performance characteristics already mentioned. Because of the Shumway dependency, we'll ship it even if we have to call it mozCanvasFilters or hide it behind a Shumway pref--do you have a preference on this? I'd rather not hide the feature as I believe it's useful for the Web at large, especially for applications currently using the Flash Player for filter effects. --Jet On Mon, Jun 15, 2015 at 4:05 PM, Xidorn Quan <quanxunz...@gmail.com> wrote: > On Tue, Jun 16, 2015 at 3:15 AM, Markus Stange <msta...@themasta.com> > wrote: > > > Summary: The "filter" property on CanvasRenderingContext2D allows authors > > to specify a filter that will get applied during canvas drawing. It > accepts > > the same values as the CSS "filter" property, so CSS filter shorthand > > functions, references to SVG filters, and chained combinations of the > two. > > > > Is there any signal from other browser vendors? It seems to me that only > Adobe and us took part in this discussion. > > I tend to vote against shipping this feature at present, as far as no spec > is written, and no other browser vendors agree with it yet. I think it > violates our guidelines. [1] > > [1] > > https://wiki.mozilla.org/WebAPI/ExposureGuidelines#When_is_an_API_ready_to_be_shipped_by_Gecko.3F > > - Xidorn > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
