New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 907141 link

Starred by 7 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

"bitmaprenderer" contexts should be supported on OffscreenCanvas

Project Member Reported by junov@google.com, Nov 20

Issue description

This seems to be an implementation oversight.  The spec says it should be exposed. It should just be a matter of:
a) Registering the factory on OffscreenCanvas in modules_initializer.cc.
b) Exposing in interface to workers in image_bitmap_rendering_context.idl

I recall that this was originally omitted because there was no known use case for it, but then we decided it should be exposed during spec discussions.

Now, I have a use case for it: The web app receives encoded png data via websocket on a worker and we want to get the data to screen as efficiently as possible. the way to do this would be to:
1) wrap the data into a blob
2) decode using createImageBitmap
3) display to an Offscreencanvas using transferFromImageBitmap
 
Status: Assigned (was: Untriaged)
Cc: fs...@chromium.org
Components: Blink>Canvas
Owner: ----
Status: Available (was: Assigned)
Another, I would hazard a guess, more common use case is the reverse scenario, going from ImageBitmap to encoded png blob (without burning GPU time).
This would also require issue 838108

Sign in to add a comment