Re: [whatwg/dom] Proposal: DOM APIs in web workers? (Issue #1217)

I raised a related issue [here](http://[discourse.wicg.io](http://discourse.wicg.io/t/proposal-support-cloudflares-htmlrewriter-api-in-workers/5721/2)/t/proposal-support-cloudflares-htmlrewriter-api-in-workers/5721/2), but that web site seems to be down (not sure if that's permanent), so I would like to make the suggestion here, if I may:

Cloudflare, which models itself after service workers, but on the server side, introduced something quite innovative:  The [HTML rewriter](https://developers.cloudflare.com/workers/runtime-apis/html-rewriter).

I think this would be a great first step in achieving more ambitious goals mentioned above.  It would provide the ability to inject dynamic data (say from IndexedDB) into the HTML stream, as the content streams into the browser.  From my experiments, having this api would allow developers to build a DOM Parser.  Perhaps such a DOM parser, built in userland, could then become a candidate for inclusion, once it proves useful and mature.  

Also, creating link preview functionality would be doable with this, and avoid an extra hop passing through a cloudflare worker.

There have been implementations with [web assembly](https://github.com/cloudflare/html-rewriter-wasm), which would seem to suggest that we would have a running start getting this implemented in the browser, and the ability to polyfill would be quite feasible.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1217#issuecomment-1694483432
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1217/1694483432@github.com>