- From: Jake Archibald <notifications@github.com>
- Date: Tue, 01 Aug 2023 01:08:29 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 1 August 2023 08:08:35 UTC
Fwiw, in [my `linear()` app](https://linear-easing-generator.netlify.app/), I wanted to be able to analyse SVG paths off the main thread. To do this, I needed to bring another implementation of SVG paths into a worker. I couldn't use the built-in APIs because there's no easy standard way to run them in a different thread. A different-thread iframe (rendered or not) would have solved this. That might be a different use-case though. In terms of DOM-in-workers, any thoughts on mine and @developit's suggestion to have a different, minimal API for this? As in, it doesn't create `HTMLImageElement`s, where you have things like `naturalWidth` and `decode()`, but a simpler tree model that can be later upgraded to real elements, and that upgrade can only happen in a document. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1217#issuecomment-1659785797 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1217/1659785797@github.com>
Received on Tuesday, 1 August 2023 08:08:35 UTC