- From: Jake Archibald <notifications@github.com>
- Date: Mon, 31 Jul 2023 04:31:04 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 July 2023 11:31:09 UTC
It feels like folks think there's a single line in browsers like: ```js if (isWorkerEnvironment) return; exposeDOMAPIs(); ``` But that isn't the case. It isn't that DOM APIs are simply not-exposed workers, it's that DOM APIs are not designed to work in non-document environments. Allowing DOM APIs to exist in workers will be a massive undertaking in terms of spec and implementation. I'm not saying it's impossible, but it's not just flipping a flag. DOM APIs are massively interlinked with style and rendering. It might be easier to create a new set of interfaces that don't have that issue, and can be cloned/transferred, and upgraded to `HTMLElement` & co within a document context. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1217#issuecomment-1658190915 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1217/1658190915@github.com>
Received on Monday, 31 July 2023 11:31:09 UTC