Develop Reference

Is Chrome microphone supposed to be not working if there is no Internet Connection?

I'm using a JS plug-in called Annyang, a Speech Recognition tool and of course it requires a working mic. Everything works just fine with normal Internet connection, but when I disable my Internet Connection, the plug in won't work at any level. (and I did check the plug-in's JS file and found nothing that needs any Internet Connection to be functioned.
Is Chrome microphone supposed to be not working if there is no Internet Connection ? Or something is wrong with the plug-in..?
Thanks a lot for reading this question. Have a good day :)

It's not the microphone that needs internet connection,
it's google's implementation of speech-recognition API, which sends the recorded data to their server to get the computed STT.
Nothing you can do on your side, not an Annyang bug either.

Is there a known issue with Safari-8 and WebSockets?

I've installed the Yosemite preview and WebSockets don't work for me on Safari 8.
The echo test page works on Chrome (with the secure checkbox set) but when I try with Safari it fails silently.
I debugged the page and what happens is that the WebSocket is created but its onopen event is not fired and the socket's readyState status remains stuck on CONNECTING (0).
I couldn't find any references to this problem, is there any configuration I may have missed that causes/fixes this?

Safari has updated (to version 8.0.10600.1.22) and the problem is now resolved.

Web worker won't start in IE unless the cache is cleared

I'm having a really weird bug in my HTML5 script. I wrote a sharepoint app completely in OData which uses a few HTML 5 webworker to do the number crunching in the background. This works perfect on all major browsers (FF, IE10+ Chrome, ...). However, when I perform a refresh or browse to the page again. The script still works as intended on FF and Chrome, but hangs on IE.
In my network view I see a request for the Worker.js file, but with a 304 NOT MODIFIED response. IE then just hangs there on that request with a status of (Pending). This issue only gets resolved when I clear my browser cache.
I correctly close all my threads with self.close().
Any idea what the issue could be? I'm not sure if it's a code issue, a browser issue or a server side issue but I can replicate the bug on Sharepoint online as well as on a local server. The whole project is JS only, so I can't modify headers as a workaround either.
UPDATE: I ran exactly the same code outside of a sharepoint environment, and it worked perfectly. Issue is Sharepoint related.

using a time based querystring parameter prevents caching showing http status 200 on each refresh. tested on latest chrome, ie, ff;
var opus = new Worker("worker.js?q=" + new Date().getTime().toString() );
to be honest this a long shot as i do not have sharepoint right now

SharePoint sends the header:
Content-Disposition: attachment; filename="xyz.js"
X-Download-Options: noopen
and the IE Web Worker Implantation then does not run this web worker. (Tested in IE11) In the IE Network Monitor the request still on pending, even the Response text is visible.
I know so fare two workarounds:
Place the web worker js in the layouts folder (needs a Farm Solution, with the downside of this)
Set the Browser File Handling for the Web application to Permissive (maybe your security is not amused)

WebSocket: onMessage() only triggered at the end when server is closing connection

I have a weird error that I can not solve.
My implementation WebSocket works perfectly. The browser connects to the server, exchange their keys and the connection is fully established! The server starts sending messages to clients (visible in the network traffic).
But on my PC, all browsers (Chrome, Firefox, portable or not), the "onMessage ()" is correctly interpreted ... but only at the end when I turn off the server! In other words, if I put an alert () to each onMessage (), during exchange, I did absolutely nothing. But once I cut the server, I receive all alerts at once!
Yet on my MacBook everything works perfectly.
This ironic is it that behavior that affects all of my browsers on my PC. I run under Windows 7.
Thank you in advance ;)

I've finally found the issue !
If you have some troubles with Websockets, just disable the SSDP discover service on Windows.
net stop SSDPSRV

I ran into a similar issue recently. web server runs a separate SSDP discovery process to find uPnP devices on the network. When I had SSDP enabled, my websocket connection was always closed. Disabling SSDP solved it. But I haven't had a chance to investigate why.

Socket.io not handling JSON in IE and Firefox

Using the example chat application here, I've written a simple Socket.IO application served over Node.Js which polls a JSON file using a fileRead from the server side and broadcasts the parsed JSON values over to the client side, where I've displaying them.
This works really well in Chrome, Safari and Opera (all those who support WebSockets).
However in Firefox, it fails until I start the Firebug console. That's when the handshake happens and the data is displayed.
In IE, it just doesn't work.
When I deploy the same code with SSL, it works everywhere. Any ideas on what I'm doing wrong here? EDIT: Now it doesn't seem to work on SSL too :(

However in Firefox, it fails until I
start the Firebug console. That's when
the handshake happens and the data is
displayed.
Sounds like this might be a console.log() problem. Firefox will hang if you call console.log() without actually having a console open.