http://blog.chromium.org/2011/08/new-websocket-protocol-secure-and.html indicates that the Chrome dev channel now has an unprefixed implementation of the WebSocket API, as far as I can tell. Also as far as I can tell, the API is not really stabilized yet (e.g. there's the big open question about whether the compression stuff is required or forbidden).

Am I missing something? Should UAs actually be shipping unprefixed websockets at this point?

-Boris

Reply via email to