Re: [whatwg] Splitting CanvasRenderingContext2D

Great, thanks all. I'll put together the start of a PR this week (just modifying the IDL) so that we can start discussing name / where everything goes. Thanks, Ian On Tue, Dec 1, 2015 at 12:11 PM, Justin Novosad wrote: > I think it may be possible to do this refactor without

[whatwg] Splitting CanvasRenderingContext2D

Hi whatwg, (public-houd...@w3.org cc'd) For the CSS Paint API[1] work in Houdini we would like to split up the current CanvasRenderingContext2D to remove references to the DOM and pixel readback. Additionally OffscreenCanvas[2] needs a similar reduced subset of the CanvasRenderingContext2D api

Re: [whatwg] Support filters in Canvas

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 =