On Wed, Jun 26, 2013 at 07:21:19AM +0200, Bas Wijnen wrote: > Control: found -1 17.0.6esr-1 > > On Fri, Jan 11, 2013 at 07:00:53PM +0100, Kurt Roeckx wrote: > > > > > > It seems that iceweasel doesn't support WebSockets while at least > > > > > > the official 10.0 version (and older) do support it. > > > > > > > > > > > > The 18.0 version in experimental also still has the same problem. > > > > > > > > > > Do you have a testcase? > > > > > > > > Some tests: > > > > http://jimbergman.net/websocket-web-browser-test/ > > > > http://html5demos.com/web-socket > > > > https://hacks.mozilla.org/2012/03/browserquest/ > > > > http://html5test.com has a test for it. > > For me, those tests also failed. However, all over the web mozilla is > claimed to support them. So I checked the source, and found that it is > a setting, network.websockets.enabled, which is on by default, but was > off on my machine. I do not know how that happened; I sure didn't > change it. > > Anyway, for people who want to fix this, you need to change it > low-level, because there is no button for it in the preferences window. > So go to about:config, look for websocket and toggle the setting. That > did the trick for me, anyway. > > Still it would be good to know why this happened, and how to make it > unhappen automatically. If there is no other way, the above workaround > should be advertised broadly, but it would be better to fix it without > user interaction, IMO.
Help > Troubleshooting informations > Reset Iceweasel should reset such settings. Note you must have done something voluntarily to end up with such a setting. Either with an addon or by yourself. Or using some particular builds of firefox and/or iceweasel. If the reset suggested above fixes it for Kurt, I'll close this bug. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
