Comment by nomsternom
5 hours ago
How would that work? I think you posted something on the github but I don't think what you're conceiving here is possible with this API. It just reroutes HTML insertions from the template to a different location, there is no duplication.
The Content-Encoding header allows any page to be a literal zip-bomb. That's how early versions of Tailwind worked; you'd deliver a 50KB Brotli payload that exploded into 2MB of CSS ( https://v1.tailwindcss.com/docs/controlling-file-size ). So pages potentially being zip-bombs is already a well-accepted part of the Web platform.
Sure, but how is this related to out of order streaming?
<div> <?marker name="placeholder2"> </div>
<template for="placeholder2"> <?marker name="placeholder1"> <?marker name="placeholder1"> </template>
<template for="placeholder1"> <?marker name="placeholder"> <?marker name="placeholder"> </template>
<template for="placeholder"> Here is some <em>HTML content</em>! </template>
Before you couldn't make this dangerous (without JS) because there was no way to auto expand the templates