Open rpavlik opened 8 years ago
There should probably be a "hey, this needs javascript" fallback. I'll look into it. Currently the backend waits for the first "ping" from the frontend before it will timeout and exit. This was to prevent timeouts from the browser taking too long to startup. Maybe we could use a longer timeout for the first ping and a shorter one for subsequent pings?
Since we're not bundling our own CEF, we do have to "take browsers as they are" - which in some cases means people will be running noscript. Are there messages to say "hey, this needs javascript" as well as some way to shut down the backend without having javascript on the front end?