3 ms·
Nobody from the WASM working group is working on that though, so the probability of direct access to the page’s DOM is close to zero. Programmers have been hopi
by austincheney 7y ago
Nobody from the WASM working group is working on that though, so the probability of direct access to the page’s DOM is close to zero. Programmers have been hoping for this for years but WASM has been very clear that isn’t in the project’s design path. The are intentional design objectives limiting that work officially but likely the largest hurdle is overcoming various security and privacy concerns already in place due to the isolation of WASM instances from their containing page.
Far more likely, and this already exists in various unofficial examples, is that WASM instances ship with a DOM for accessing markup provided by or requested into the WASM instance.
- justinclift 7y ago> ... WASM instances ship with a DOM for accessing markup provided by or requested into the WASM instance. Sounds like it would achieve the same end goal? eg direct access to the page elements, without needing to go through JS Or is that my not really understanding the problem space? :)
- austincheney 7y agoNo, a DOM that is provided by a WASM instance will provide access to markup contents available to that WASM instance, such as markup requested or shipping with the WASM code, but not outside the WASM instance such as the containing page.
- justinclift 7y agoInteresting. What's the intended use case for that? Trying to think of something, but nothing is coming to mind.
- austincheney 7y agoIf your WASM application makes use of any kind of XML or HTML content you need to parse it or it’s just a string.
- justinclift 7y agoNo worries, thanks. :)