- From: Noam Rosenthal <notifications@github.com>
- Date: Thu, 04 Jan 2024 02:25:08 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 4 January 2024 10:25:15 UTC
To demonstrate how this doesn't expose new ancillary data, consider the following. You want to know if other frames in the process are blocking. To do that today, you can run: ```js const before = performance.now(); setTimeout(() => { const delay = performance.now() - before; }, 0); ``` Same with a `requestAnimationFrame` if you want to measure rendering delay in particular. To do that with LoAF, you'd have to register an observer, and make sure that the delay surmounts to more than 50ms. This makes LoAF a very blunt instrument to measure things that can be measured in a sharp way today... -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/911#issuecomment-1876854462 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/911/1876854462@github.com>
Received on Thursday, 4 January 2024 10:25:15 UTC