- From: Xiaocheng Hu <notifications@github.com>
- Date: Thu, 15 Jan 2026 01:57:52 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 15 January 2026 09:57:56 UTC
xiaochengh left a comment (w3ctag/design-reviews#1013) Hi @noamr, the TAG discussed it today and found some new concerns: We are aware that the "presentation time" is not well defined, and an accurate definition might be out of the scope of the Web specs. However, the "paint time" as how it's currently defined is not perceivable by the end user. It's somewhere in the middle of the entire rendering pipeline, and there might be an arbitrary delay between this and when the pixel actually shows up on the screen. For this reason, we are unsure whether this "paint time" is a good enough performance indicator to add to the platform. We are also wondering if new timings in the rendering pipeline could be used to perform side-channel attacks, e.g. exfiltrate canvas data to someone else. Have you considered alternatives that are more interoperable and better match the page performance from the end users' perspective? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1013#issuecomment-3753859823 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1013/3753859823@github.com>
Received on Thursday, 15 January 2026 09:57:56 UTC