<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 2, 2016, at 2:59 PM, Dean Jackson <<a href="mailto:dino@apple.com" class="">dino@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 3 May 2016, at 7:04 AM, Rik Cabanier <<a href="mailto:cabanier@gmail.com" class="">cabanier@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, May 2, 2016 at 1:58 PM, Simon Fraser <span dir="ltr" class=""><<a href="mailto:simon.fraser@apple.com" target="_blank" class="">simon.fraser@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">On May 2, 2016, at 1:45 PM, Rik Cabanier <<a href="mailto:cabanier@gmail.com" target="_blank" class="">cabanier@gmail.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">All,<div class=""><br class=""></div><div class="">with the release of DCI-P3 screen, WebKit began supporting the display of high gamut images.</div><div class="">Specifically, if you have an image with a DCI-P3 profile, its pixels render untouched on the new displays.</div><div class=""><br class=""></div><div class="">However, if you try do do any sort of canvas manipulation, you will see that the colors are being compressed to sRGB and you will lose the depth of the color.</div><div class=""><br class=""></div><div class="">Was it an oversight to always create the canvas imagebuffer in sRGB? [1]<br class=""></div></div></div></blockquote><div class=""><br class=""></div></span>No, this was a deliberate choice. We can't change author expectations for what getImageData() return.</div></div></blockquote><div class=""><br class=""></div><div class="">Now we see different visual output which is also not what an author expects :-(<br class=""></div></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">Since there is no way to create a canvas element with pixel data that is interpreted to be in anything other than sRGB, this behaviour seems expected to me. I'm not sure what else could happen? We couldn't magically make all the canvas elements in the page use P3. If we did that, they wouldn't match the CSS content.</div><div class=""><br class=""></div><div class="">The fix is coming: a way to tag the colorspace of the canvas element.</div></div></div></div></blockquote><br class=""></div><div>Also a way to specify that you want deep backing store:</div><div><<a href="https://github.com/whatwg/html/issues/299" class="">https://github.com/whatwg/html/issues/299</a>></div><div><br class=""></div><div>Simon</div><div><br class=""></div><br class=""></body></html>