I'm sorry to hear that; good luck with the other web service!
As for your comments regarding Chrome support: the WoL client has absolutely nothing to do with the browser you use. Java Web Start is launched *outside* of the browser, as a completely separate program. An issue like this one is caused by misconfiguration, either of Java or your OS' file associations.
Furthermore, I regularly use Chrome to browse WoL and launch its client. This does, however, require me to manually click the downloaded JNLP file as Chrome saves the file by default instead of opening it. That it does work seems to be confirmed by the ~12% of our users using Chrome (source: Google Analytics).
Again, I'm sorry you couldn't find the cause of this issue, but I suspect it's caused by a client-side configuration error. If it weren't we'd have seen many more bug reports than we have. Most of the ones we've seen were caused by outdated Java installs, incorrect settings or a lack of a tutorial on how to launch a JNLP file.