The "Runner" now try to connect to websocket using "ws://" (first), and fallback to "wss://" (second).
Thus, this new Runner should work OOTB on repl.it, idx.dev or glitch.com, without the need of htagweb.
On theses platforms, the webserver is over SSL. So you'll need to use htagweb, where you can force the socket to use SSL with an option. But you'll need to explicitly force the server to use one or the other. (BTW it makes sense to use htagweb if you want to serve your app for many different users ... htag default runner is only for one user at a time)
Now, the default htag "Runner" should work, because it will implicitly try one and fallback to the second.
By default, it try "ws://", because the goal of the default Runner, is for desktop/android app, where SSL is not mandated (one client, one server). But now, it should work implicitly OOTB in a ssl webserver context.
(Perhaps, in the future, htagweb will introduce the same kind of mechanism ... but now, you should explicitly define it in the htageweb runner ... but I don't wanted to add this kind of option in the default htag Runner ... KISS first!)
**UPDATE** :
- it's validated https://idx.google.com/ : it works now OOTB ;-)
- the trouble seems more complex for repl.it ;-( ... need to dig that