Re: Using Spidermonkey as a browser JS content back-end

On Saturday, March 25, 2017 at 6:18:41 PM UTC+1, Andrew Sutherland wrote:
> I don't think this is feasible.  There is no JS execution context
> exposed to content that does not include interaction with the DOM
> bindings an through them the entire platform.

Yeah that's what I was afraid of. I'm curious then what the Waterfox developer meant when he said he used the standalone Spidermonkey lib for specialized versions of his browser.

Would it be possible to use the standalone Spidermonkey as a drop-in replacement for the in-tree version of JS then, to handle both chrome and content, or is that just as unfeasible?
Of course any jsapi changes between versions would have to be addressed then, to make the DOM align with changes in JS, but I think that's going to be less complicated than trying to follow the wildly-twisting development path Spidermonkey has taken (and probably will continue to take). or am I wrong there?

As said it's a little silly to keep re-inventing the wheel when Spidermonkey as-is is already quite complete in terms of how it handles the latest ES standards.