Bug? IE9 - reply, quote, chat etc buttons don't appear to work
-
Hi guys,
We're currently testing a v0.5.4 installation on a vanilla IE9 browser (using a VM from https://www.modern.ie) and we appear to be getting odd behaviour. The site renders fine, appears to be responsive to size changes as expected and basic category/topic navigation works fine. However, various buttons on the site (New Topic, Reply, and the per-reply Chat, Reply, Quote etc) don't appear to do anything.
I did search for discussions around IE9 support but only found a few old posts regarding IE8 - the implication being that IE9 is supported. Is this actually the case?
Thanks
-
Hi,
Yeah sorry - should have done that in the first place.
There are no errors in the console (and no 404/500s on the network panel either), either on page load or when one of those buttons are clicked: it's as if they haven't been wired up to anything.
[initially there was a javascript error on page load regarding Flash - which I understand is because IE9 doesn't support web sockets - even though it's actually using XHR polling. I've installed the flash player and the error has disappeared]
-
@julian said:
Looks like we'll have to fire up BrowserStack
Good luck with that.
Browser testing service BrowserStack has temporarily suspended its services while it recovers from a "hack attack" by someone apparently bent on discrediting the security of the widely used tool.
Someone sent out an email last week claiming to be from browserstack claiming they were shutting down due to outright lies in their terms of service.
You can read the email here
-
Hi,
I've applied that commit (and the subsequent IE8 fix in the same if clause), and it appears to work: the buttons now work as expected, although we are seeing very odd socket.io behaviour (constant disconnect/reconnect) which I'm trying to track down, so I can't confirm this fixed 100%
Thanks for the fast turn around!
-
No - just a single instance. I traced the socket.io problem to a plugin that'd been updated via npm to a version designed for 0.6.0 whereas we're running 0.5.4.
The nodeBB child process was constantly being restarted which manifested itself as constant reconnects on the clients.