Re: [whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

2016-01-26 Thread Kenneth Russell
That's right. From discussions with Mozilla I don't think that code path's enabled in their implementation yet, but it will be (as well as in Chrome's future implementation of the same spec). On Sat, Jan 23, 2016 at 12:40 PM, Gregg Tavares wrote: > Never mind me. For

Re: [whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

2016-01-23 Thread Elliott Sprehn
I presume you're supposed to just postMessage back to the main thread when you commit(). The spec should probably have a "commit" event though. On Jan 23, 2016 1:49 PM, "Gregg Tavares" wrote: > I just noticed Firefox shipped an OffscreenCanvas implementation. Looking > at the

[whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

2016-01-23 Thread Gregg Tavares
I just noticed Firefox shipped an OffscreenCanvas implementation. Looking at the spec it seems there is no way to synchronize updates from a worker with dom/css manipulations. Was this already discussed? There are web apps that synchronize HTML dom elements with canvas updates. I'm sure they'd

Re: [whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

2016-01-23 Thread Gregg Tavares
Never mind me. For whatever reason my mind blanked out. You can transfer to the main thread and then apply to a canvas.