Issue metadata
Sign in to add a comment
|
incorrect color space handling for ImageData
Reported by
oss...@cendio.com,
Apr 24 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Create an ImageData object (constructor or createImageData() doesn't matter) 2. Fill with srgb data 3. Call putImageData() What is the expected behavior? Correct SRGB colors. What went wrong? Colors are much darker than expected. An unwanted SRGB to linear conversion is performed at some stage. This can be verified by doing the opposite conversion before feeding data to Chrome. Did this work before? Yes Unsure, most likely 55 Chrome version: 57.0.2987.132 Channel: stable OS Version: 7.1.2 Flash Version: Bug only happens when the canvas is large, so there seems to be multiple code paths. Likely suspect: https://chromium.googlesource.com/chromium/src/+/96126d211 This makes noVNC almost unusable on Chrome, so I would very much appreciate a high priority on this. Or a possible workaround. It doesn't help specifying color space to getContext() or createImageData().
,
Apr 24 2017
Disabling "Accelerated 2D canvas" from chrome://flags avoids the issue. So it does seem like it's the GPU path that is buggy. Is there some way we can avoid the GPU via Javascript?
,
Apr 24 2017
,
Apr 24 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by oss...@cendio.com
, Apr 24 2017