The current canvas filters proposal [1] allows using SVG reference filters
defined in external documents (e.g. “url(file.svg#filter)”). Since the
external document needs to be loaded before the filter can be applied,
there’s a delay between setting the context’s filter attribute to such a
filter
On Fri, Feb 26, 2016 at 10:40 AM, Anne van Kesteren
wrote:
> On Fri, Feb 26, 2016 at 4:34 PM, Ali Juma wrote:
> > The current canvas filters proposal [1] allows using SVG reference
> filters
> > defined in external documents (e.g. “url(file.svg#filter)”).
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Anne van
Kesteren
> Perhaps we could support assigning an SVG filter directly (as an object)?
> Developers would be responsible to load them if they're external. Adding yet
> another network API that's a thin layer on top of
On Fri, Feb 26, 2016 at 4:34 PM, Ali Juma wrote:
> The current canvas filters proposal [1] allows using SVG reference filters
> defined in external documents (e.g. “url(file.svg#filter)”). Since the
> external document needs to be loaded before the filter can be applied,
>
Having an opaque handle (CanvasFilter) would be great for Houdini paint.
This would mean that when we plumb in a property of CSS type
the TypedOM can have an opaque handle to that
filter. I.e.
registerPaint('x', class {
paint(ctx, styleMap) {
const filter =