Contact emails
aj...@chromium.org, ju...@chromium.org
Spec
https://html.spec.whatwg.org/multipage/scripting.html#filters
Summary
A string attribute 'filter' on CanvasRenderingContext2D to apply effects to primitives drawn to the canvas. The attribute is parsed the same way as CSS filters.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/hx5g-yHS45I
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Debuggability
No special debugging support is needed.
Interoperability and Compatibility Risk
Firefox has implemented this feature behind a flag. There are no public signals from Internet Explorer or Safari.
Compatibility risk is low. This is a new API, so doesn’t affect web content that doesn’t use it.
OWP launch tracking bug
Entry on the feature dashboard
https://www.chromestatus.com/features/6701649301078016--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
Since we're the first to ship (behind a flag doesn't count), I feel compelled to apply a little extra rigor and ask: what's the status of the Mozilla implementation? Are they happy with the state of the spec? Has anyone attempted to test the interoperability between the blink and Gecko implementations?
While not entirely related, it feels a bit awkward to have an officially supported API for canvas filters while CSS filters (which use the same syntax and give a similar effect, only on all of the elements) are still unofficially supported (prefixed). Is shipping unprefixed CSS filters on the short term table?
And perhaps related - are there CSS filter issues that prevent Blink from unprefixing that also affect canvas filters?
LGTM3.