- From: Xiaocheng Hu <notifications@github.com>
- Date: Mon, 19 Jan 2026 23:33:16 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 January 2026 07:33:20 UTC
xiaochengh left a comment (w3ctag/design-reviews#1183) Hi @Clqsin45, the TAG discussed it at a breakout today and found that a middle ground between `prefetch` and `prerender` will help. Avoiding execution of non-essential scripts looks desirable, especially when considering analytics and ads. Since this is an early review, we'd like to see more research into real world scenarios and more alternatives considered. In particular: - What about a `preparse` action, namely, trying to parse the document (up to parser-blocking script) without rendering it? - What types of subresources to load, and do we need finer control here? For example, some ads may use pixels for tracking, for which loading images might be bad - How many pages will benefit from `prerender_until_script` (or any alternatives)? A real world study (over e.g. HTTP Archive) will be greatly helpful, as we (and developers) need to understand the target use cases and limitations of each strategy. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1183#issuecomment-3771436754 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1183/3771436754@github.com>
Received on Tuesday, 20 January 2026 07:33:20 UTC