Auto game joining with Google Chrome "was" working at some stage, at least for me?
You can only get chrome to start one application at time. Either mumble or the game. We decided to let it do auto connect to mumble (on mumble required lobbies) because we felt like it is more important to be on mumble automatically and users will join the game on their own (by clicking the "Join game" button).
In case it is a lobby without mumble required, chrome will still auto connect you to game.
Mumble auto join in Chrome works fine unless I already have mumble connected, in which it either:
- Connected to a non TF2Center Mumble, autojoin begins, disconnect from current server, connect to TF2Center mumble, joins root channel
- Connected already to TF2Center Mumble, autojoin begins, disconnects from server, connects to TF2Center mumble again, requests registered user password
We are aware of this problem but do not have a solution for this right now. This probably requires us to know if the user is already running mumble or not which is not trivial.
Like you mentioned, there isn't much you can do about that however clicking the join mumble button manually before a pug begins to chat with others pre-pug only to be disconnected forcibly and reconnected incorrectly is fairly annoying. Perhaps grey out the mumble join button until the pug starts for manual reconnects.
This can be easily fixed by disabling auto connect to mumble in case the user clicked the "join mumble" link before the game started and will be considered. Thanks for the idea!
What exactly is the technical limitation of Chrome is that is preventing both auto server join? Chrome as mentioned did at one stage autojoin TF2 servers?
First: It is not about autojoining tf2. It is about auto joining mumble and tf2 at the same time.
We are changing the src of an iframe to steam:// or mumble:// which results in the URL being loaded by the browser and the application to start. But chrome won't execute it's "start application routine" if you do this multiple times in a row. There is a big timeout of multiple minutes until chrome let you start an application this way again. It is probably to prevent websites from spamming you with application start requests. Other browsers do not show such behavior.