Playground: Add chromium support

[adelhult]

Resolves GH-45. This PR adds support for the playground in Chromium browsers. This is done by instantiating the WASM module that contains the compiler inside of a web worker instead of the main thread.

[github-actions]

PR Preview Action v1.3.0
Preview removed because the pull request was closed.
2023-03-12 19:00 UTC

[CMDJojo]

Nice! Good job on the fix! However, I think we should change to import the script using ECMAScript module syntax since it looks cleaner, doesn't pollute the scope with stuff we don't know about, and have cleaner syntax overall when calling the functions. Firefox will support it in version 111, which is released March 14th. This won't require changes to wasm-pack and so on, and is generally the preferred way to do it!

[CMDJojo]

Also, this does not work...I think you failed to commit the --no-modules hack to get around ES module syntax. Doesn't run on FF110.0.1 on Windows 21H2

[adelhult]

Yeah, noticed that too, forced push a change a few seconds ago.

[adelhult]

Nice! Good job on the fix! However, I think we should change to import the script using ECMAScript module syntax since it looks cleaner, doesn't pollute the scope with stuff we don't know about, and have cleaner syntax overall when calling the functions. Firefox will support it in version 111, which is released March 14th. This won't require changes to wasm-pack and so on, and is generally the preferred way to do it!

Opened #152!

[CMDJojo]

I would love it if you made it render on load again as it did before, as it is a nice welcoming screen when the example document gets loaded

[adelhult]

Hmm, I thought I fixed that again. Will take a look!

[CMDJojo]

I still get the same problem sometimes, I think we still have a race condition between the document fetch and the parser/core loading, possibly... It would be nice to get this resolved before pushing something that works sometimes. (FF110.0.1 on Windows 21H2)

[CMDJojo]

We might be able to solve this by fetching/displaying the welcome document strictly after we have loaded the core wasm, by sending an init event to the main (sync) JS. Or let the worker fetch the document itself

[CMDJojo]

It seems like your last commit solved the problem. I think we are ready to merge it, but we should PR #152 asap to merge it on tuesday when the Firefox update goes stable and we can verify that ES modules work there as well! (Approved)