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

I'd be curious to know which element might have issues though, as I think most of them need to be adopted and pass through the `adopt` algorithm before having any meaning for the current environment ... I've tested `<base>`, custom elements, others, I can't find anything working at all unless adopted by the "*live document*". MDN also doesn't specify anything around this behavior and standards mention that *scripts* will be flagged as not-executable https://html.spec.whatwg.org/multipage/dynamic-markup-insertion.html#dom-domparser-parsefromstring-dev

that's still something to consider while adopting those nodes ... moreover:

> The document's [encoding](https://dom.spec.whatwg.org/#concept-document-encoding) will be left as its default, of [UTF-8](https://encoding.spec.whatwg.org/#utf-8). In particular, any XML declarations or [meta](https://html.spec.whatwg.org/multipage/semantics.html#the-meta-element) elements found while parsing string will have no effect.

In the [parsing model](https://html.spec.whatwg.org/multipage/parsing.html#overview-of-the-parsing-model) it's also not clear why this would be unsafe if the document is created via the API ... looking forward for some enlightenment around this.

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

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