- From: Chris Needham <chris.needham@bbc.co.uk>
- Date: Wed, 8 Feb 2023 21:07:44 +0000
- To: Pierre-Anthony Lemieux <pal@sandflow.com>, "public-colorweb@w3.org" <public-colorweb@w3.org>
Hi Pierre, > Is there a concrete timeline for Float16Array, which would cause the Color CG to revisit its recommendations? Can we answer this question rather than ask Anne? Can we progress Float16Array within TC39? It's currently a stage 1 proposal: https://github.com/tc39/proposals/blob/main/stage-1-proposals.md See https://tc39.es/process-document/ for description of their process stages. Here's the last discussion in TC39, from 2017: https://github.com/tc39/notes/blob/HEAD/meetings/2017-05/may-23.md#16ig-float16-on-typedarrays-dataview-mathhfround-for-stage-1 and discission prior to that: https://esdiscuss.org/topic/float16array There were open questions, can we help answer them to move the proposal forward? Thanks, Chris -----Original Message----- From: Pierre-Anthony Lemieux <pal@sandflow.com> Sent: 08 February 2023 18:59 To: public-colorweb@w3.org Subject: WHATWG comments re: Float16Array + HTML Canvas Good morning/evening, FYI. See the comment at [1]. [1] https://github.com/whatwg/html/issues/8708#issuecomment-1423026968 I suggest we reply. Below is a first pass at such a reply: """ - the objective is to achieve bit depth greater than 8 bit in Canvas, which is needed for native HDR imagery, among other things. This is needed today. - the suggestion to add support today for Float32Array today was with the understanding that support for Float16Array could not be added today because it required a change in JS Is there a concrete timeline for Float16Array, which would cause the Color CG to revisit its recommendations? """ Please provide feedback by Monday COB. Best, -- Pierre
Received on Wednesday, 8 February 2023 21:08:52 UTC