> We updated WIAB to r1241411 a few days ago, not sure if it is related. When > opening a wave with Firefox 10, the wave view stays in "loading" state. I get > the following debug output in the server: This was after my SSL patches were comitted (r1241106 < r1241411) (with a known missing patch needed for Socket.IO in SSL conditions that wasn't put in the Apache codebase) Did you try to turn SSL on?
> Using SocketIO: NB: The socketio related config option is only a suggestion (eg. any browser that fully supports websockets will ignore it with the current codebase). Also, note that your 'using websockets' error code was still all about Socket.IO -> using XHR-Multipart (because of the above situation). > I suppose this is related to incomplete Websockets support in Firefox 10? Sort of... I know that they used to use the 'window.MozWebSocket' API for a while, whilst the WIAB codebase only checked for the 'window.Websocket' API. (Perhaps v11 changed to use this?) > (By the way, before this we also had problems with special characters like > German umlauts, which were broken in Firefox.) I have noticed this too, notably around pound (currency) signs. It doesn't look like there is a report in Jira yet for this though... I will create one now. Ali
