- From: Jake Archibald <notifications@github.com>
- Date: Mon, 31 Jul 2023 04:22:27 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 July 2023 11:22:32 UTC
@BenjaminAster > That seems a bit... clunky? Coming from a worker… Yeah, that's fair. If your starting point is a worker, the iframe solution isn't great. But, maybe being able to create one of these iframes from a worker is a solution. > At the end of the day, using an iframe for that is a hack, and not what iframes were designed to do. I don't find this very compelling. You could equally, and truthfully say that DOM APIs weren't designed to be in workers. Whatever solution is employed here will involve changing the intentional design of something. > DOMParser & friends are not something that are architecturally coupled to the main thread Yes they are. They're absolutely coupled to documents. That's why they aren't available in workers. Maybe their design could be changed so they don't need to be coupled to documents, but isn't where we're at right now. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1217#issuecomment-1658180058 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1217/1658180058@github.com>
Received on Monday, 31 July 2023 11:22:32 UTC