- From: Lea Verou <notifications@github.com>
- Date: Wed, 23 Jun 2021 05:02:52 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 23 June 2021 12:03:31 UTC
> Yeah, that's correct. Thank you. Is it correct to assume it would throw with the same error in subsequent calls to `getContext()`? I.e. ```js let ctx = canvas.getContext("2d", {colorSpace: "display-p3" }); let ctx2 = canvas.getContext("2d", {colorSpace: "flugelhorn" }); // throws? ``` Another question that came up in a breakout this week. I do see some examples in the explainer use a media query to decide which color space to use. I assume however that the canvas color space and the display device color space are entirely decoupled, and therefore it's entirely possible to work on a P3 canvas, in a less capable (e.g. sRGB) display device. You would obviously not _see_ the non-sRGB colors, but the underlying numbers would be unaffected. Is my assumption correct? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/646#issuecomment-866776648
Received on Wednesday, 23 June 2021 12:03:31 UTC