Socket.io doesn't work on Chrome and Firefox - node.js

I'm new to node.js and socket.io. I test sample applications that posted on http://socket.io/#how-to-use. Everything's fine on Opera, IE and Safari but nothing happens on Chrome and Firefox.
Versions
Node.js - v0.10.5
Socket.io -0.9.6
Chrome - 27.0.1453.116
Firefox - 21.0

That is a bug around Web Socket and some modern browsers.Even this test will not work. Read the following issues.
https://github.com/LearnBoost/socket.io/issues/1150
991 and 998

Related

Audio chat using webrtc in safari browser?

I was searching for some solution for audio chat between two users in safari browser Using WEBRTC(Peer js). I have found some solutions using temasys plugins , but they only work for local streaming.
Is there someway in safari browser.
Yes, you can use Temasys plugin for Mac OSX safari and IE. I have used temasys successfully for these browsers on a live site though there are random issues sometimes. And now, I think peerjs supports Temasys integration also.
Things are about to change.
Apple announced support for WebRTC in Safari 11.
You can download the latest beta version of Safari 11 at the following link:
(You need to sign in with your Apple ID) https://developer.apple.com/safari/download/

Layout issue in Safari 7.1 and 8

I have a simple SharePoint Web Application which have no issue or bug, until a client open it in Safari browser version 7.1 on Mac OS 10.9 Mavericks a month ago.
Since I don't have any Mac OS, then I tried to open the web via browser emulator in http://www.browserstack.com/ and found that the problem is only happen in Safari 7.1 and 8 (no matter what the device, MacOS, iPad, or iPhone6)
When we open it using Google Chrome, Firefox, IE any version, even Safari 6 or older, it looks okay.
But when we open it using Safari 7.1 or later, the menu bar looks like wrecked.
Is anyone know how to fix it?
I've did deep research and found the main problem. It's not about the layout code, but the problem is compatibility between my old SharePoint 2007/2010 with the new Safari browser 7.1 or later.
The problem fixed by this thread:
ASPMenu in Safari 7.1 Not Rendering Properly in SharePoint 2010

Cross Browser Support for Coded UI

I have Recorded Coded UI Test With Silverlight 5 Application With IE Browser. but when i am trying to Run it for Chrome it's not working.
For non silverlight application it is working fine.
I have installed Cross Browser plugin for chrome.
As per my comment, Cross browser testing is only for web applications. Silverlight testing is not supported in Chrome or Firefox.
Since Silverlight is a browser plug in, if something works in Silverlight/IE then you can rely on it working in FF and Chrome. If it fails then it's a problem with Silverlight, not your application.

change browser for sencha touch 2

We are developing an app with Sencha Touch 2 and PhoneGap 2.0. We also want to use WebGL.
But neither the android browser nor safari mobile supports it.
However Opera Mobile 12 supports WebGL. Is it possible to start the sencha app with Opera Mobile?
Firstly, PhoneGap overrides the capability of Native Android browser. We cannot use the Opera Mobile browser features for developing the PhoneGap Applications.
Secondly, Sencha Touch is not supported by Opera Mobile. It runs only on WebKit browsers. I am not sure about Mobile chrome. But any other browser except android default browser will not able to run all features of sencha.
Hope you got your answer.
You can try RhoElements v1 browser. It also only supports WebKit as far as I know.
https://docs.symbol.com/ReleaseNotes/RE_0100001000_ReleaseNotes.html
http://www.spritle.com/blogs/2012/01/04/rhodes-3-3-x-supports-motorola-rhoelements-and-android-et1/

Browser support by Watir

I know that Watir supports Firefox and Chrome.
Does someone know which versions of Firefox and Chrome are supported?
According to Watir web site they support Firefox 5 and that is a pretty old version.
As far as I know, Watir supports all recent versions of Internet Explorer, Chrome, Firefox, Safari and Opera.
At work, with the Webdriver backend, I had to downgrade from Firefox 13 to Firefox 10.0.2. That seems like a big difference, but they have been cranking out the FF versions lately. It's probably because of a change in port, but I am just speculating.

Resources