Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On May 1, 2016 1:08 PM, "Rik Cabanier" wrote: > > Great to hear! > Are there minutes posted? As far as I know, the minutes and mail archives are visible to members only. I'm working to capture what we have so far and to move the discussion to a broader and more visible forum.

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

Great to hear! Are there minutes posted? On Sunday, May 1, 2016, Justin Novosad wrote: > There is currently an ongoing discussion with the Khronos Web3D group to > develop a proposal that solves these problems in canvas, over the past few > weeks we have converged on a

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

There is currently an ongoing discussion with the Khronos Web3D group to develop a proposal that solves these problems in canvas, over the past few weeks we have converged on a solution that I think is pretty solid. I am in the process of writing-up the HTML (non-WebGL) part of the proposal and I

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 6:35 PM, Ron Waldon wrote: > What if we could just declare the colour-space that content uses, and > allow the browser to make a best-effort translation if the current display > uses a different colour-space? > That is pretty much the situation in

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

What if we could just declare the colour-space that content uses, and allow the browser to make a best-effort translation if the current display uses a different colour-space? This way, we don't need to expose colour profiles or other fingerprinting details to JavaScript code. That code can just

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 4:27 PM, Rik Cabanier wrote: > > > On Sat, Apr 30, 2016 at 3:25 PM, Kornel wrote: > >> >> On 30 Apr 2016, at 21:19, Rik Cabanier wrote: >> >>> >>> > It would be ideal if we can specify that the canvas backing

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

> On 30 Apr 2016, at 21:19, Rik Cabanier wrote: > > > It would be ideal if we can specify that the canvas backing store is in the > > device profile. > > How would the website know what profile this is? If it's just a boolean > setting, then I don't see how it would make

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 12:38 PM, Kornel wrote: > > > On 30 Apr 2016, at 19:07, Rik Cabanier wrote: > > > > It would be ideal if we can specify that the canvas backing store is in > the device profile. > > How would the website know what profile this is?

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

> On 30 Apr 2016, at 19:07, Rik Cabanier wrote: > > It would be ideal if we can specify that the canvas backing store is in the > device profile. How would the website know what profile this is? If it's just a boolean setting, then I don't see how it would make it

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

[Sorry to revive this old thread] All, with the advent of DCI-P3 compliant monitors and Apple's Safari doing color managing to the device, we're seeing some issues in this area. - Currently, WebKit sets the profile of the canvas backing store to sRGB regardless of the output device. Because of

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Thu, May 22, 2014 at 4:09 PM, Rik Cabanier caban...@gmail.com wrote: Well, the issue with not having a standardized intermediate colorspace, is that output will look different on different devices. I theory, that should only be the case when drawing raw values through putImageData.

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

Hi justin, thanks for this explanation! On Thu, May 22, 2014 at 12:21 PM, Justin Novosad ju...@google.com wrote: tl;dr: The color space of canvas backing stores is undefined, which causes problems for many web devs, but also has non-negligible advantages. So be careful what you wish for.