This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
See the discussion at: http://lists.w3.org/Archives/Public/public-fx/2011OctDec/0108.html
I don't see how running a shader on a web worker helps anything. You have to run them at paint time, and you're blocked waiting for painting then.
The "MediaStream Processing API" proposal offers an example of Workers for audio processing. The document does not tackle video processing though it does offer the idea of <canvas> processing in the examples section. It's noted that video data should be added in a subsequent draft to the ProcessMediaEvent. https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html#worker-processing Shaders may be used for audio processing, this is an area where the CSS Shaders proposal and the MediaStream Processing API have some possible overlap. GLSL can be used for Audio effects, and JS can be used for image effects.
(In reply to comment #2) > The "MediaStream Processing API" proposal offers an example of Workers for > audio processing. The document does not tackle video processing though it > does offer the idea of <canvas> processing in the examples section. It's > noted that video data should be added in a subsequent draft to the > ProcessMediaEvent. > https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing. > html#worker-processing > > Shaders may be used for audio processing, this is an area where the CSS > Shaders proposal and the MediaStream Processing API have some possible > overlap. GLSL can be used for Audio effects, and JS can be used for image > effects. I don't disagree that shaders as a technique can be used for GPGPU, but this is not the purpose of CSS Shaders. I agree with Simon that it does not make any sense to combine WebWorkers with CSS Shaders. I close this bug for now.