Release 26 disables "comms" box(es) in Kixeye Battle Pirates Game.
Firefox 26 killed the comms boxes in the Facebook game by Kixeye, - the comms absolutely do not work. Using the game in Internet Explorer allows comms functionality, so this is not an Adobe Flash player problem. Everything worked fine in version 25.0.1.
Wszystkie odpowiedzi (2)
I'm guessing from the version indicating in the sidebar to your post that you've switched back to Firefox 25 and the chat feature works again??
According to recent discussion on KIXEYE forums, there might be a mixed content blocking issue. See: UPDATE KILLED COMMS!! - KIXEYE.com (most of the earlier pages of the thread are about problems that started on Dec. 11th).
If you see a gray "shield" icon in the address bar to the left of the site address, this indicate that there is some insecure content in the secure page. This article has more information: Mixed content blocking in Firefox Note: you need to exit Full Screen view to see the address bar.
To see the source of the insecure content, you can open the Browser Console (Ctrl+Shift+j) and filter the list by typing mix in the box at the upper right. If the source is a trusted site, you can click the shield icon to make an exception for the page.
If that is necessary in Firefox 26 and not Firefox 25, it could mean that a loophole in this feature was closed, or the definition of "active content" was changed. I guess we'll find out over time exactly what it was.
Or if that turns out to be completely irrelevant, we'll keep searching.
Zmodyfikowany przez jscher2000 - Support Volunteer w dniu
Yes, I have switched back to version 25.0.1 and the chat / comms feature now works as it always did.
In addition to the chat feature I use Rapport Trusteer product to essentially create a VPN tunnel between my machine and my bank's server, making it ultra secure. So, I cannot say whether there is insecure data intermingled with secure data, but in the VPN environment, I would highly doubt it.
Also with the bank software, but when Firefox is later updated, my approach has been to install the newer version(s) until one of them finally allows all three systems to work together. For example, the same condition occurred in all versions of release 23 - I had to jump from a release 22 build to a release 24 build, and later the original release of 25.0.0 would also not work properly.
Hope this added information may help narrow the challenge.