W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2016

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

From: Rik Cabanier <cabanier@gmail.com>
Date: Sat, 30 Apr 2016 23:22:22 -0700
Message-ID: <CAGN7qDBnLBccKZ-203JD9TONtd23M7kPrV_8asFvAj3OCyDuAQ@mail.gmail.com>
To: Ron Waldon <jokeyrhyme@gmail.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>
On Sat, Apr 30, 2016 at 6:35 PM, Ron Waldon <jokeyrhyme@gmail.com> 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 Safari today.
My original points are about some deficiencies in the canvas implementation
for this workflow.


> This way, we don't need to expose colour profiles or other fingerprinting
> details to JavaScript code. That code can just declare that it uses Adobe
> sRGB (which might be the default if not specified?), and the browser can
> apply a transform as needed depending on the hardware.
>

I am not convinced that this is a fingerprinting concern, especially if we
just allow generic names for profiles.
Certainly the additions to CSS wrt color and media queries allow you to
infer the used profile


> The declaration could be a MIME-type parameter, for visual content
> delivered via HTTP, or there could be a Canvas attribute or constructor
> option. /shrug
>
Received on Sunday, 1 May 2016 06:22:47 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:38 UTC