More robust webworker fallbacks

[taisel]

Some browsers like Google Chrome do not allow webworkers on localhost via opened file:///. Google Chrome also does not allow spawning webworkers inside of webworkers. We need to introduce proper code flow that isn't hacky to handle these cases.

[taisel]

c30d730
e2c4adc

[taisel]

c30d730
e2c4adc

[taisel]

Only issue now is that we have to user-agent sniff for the renderer thread creation still.

[taisel]

Only issue now is that we have to user-agent sniff for the renderer thread creation still.

[taisel]

Probably should just make it a user setting whether or not to box the cpu thread in a separate thread. The user agent sniffing will fill in the default value for it, but it'll be user-overridable. The consequence of such is that if chrome hits the creation limit, the renderer will be on the same thread as the cpu thread, which will be in a separate thread from the main thread.

[taisel]

Probably should just make it a user setting whether or not to box the cpu thread in a separate thread. The user agent sniffing will fill in the default value for it, but it'll be user-overridable. The consequence of such is that if chrome hits the creation limit, the renderer will be on the same thread as the cpu thread, which will be in a separate thread from the main thread.

[taisel]

Done.

[taisel]

Done.