joshua
/
websockify
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
websockify/docs/browsers.md

3.7 KiB
Raw Blame History

noVNC: Browser Support

Ubuntu Karmic (9.10)

Browser Status Performance/Notes
Chrome 7.0.510.0 Broken WebKit render bug (see note 3)
Chrome 5.0.375.29 Excellent Very fast. Native WebSockets.
Firefox 4.0 Beta 6 Excellent Fast. Native WebSockets. SSL cert hassle (see note 2)
Firefox 3.6.1 Good Slowed by web-socket-js overhead. Local cursor causes segfault.
Arora 0.10.1 Fair Slow due to broken putImageData and web-socket-js.
Opera 10.60 Poor web-socket-js problems, mouse/keyboard issues (see note 1)
Konqueror 4.3.2 Broken web-socket-js never loads

Ubuntu Jaunty (9.04)

Browser Status Performance/Notes
Chrome 5.0.375.29 Excellent Very fast. Native WebSockets.
Firefox 3.5 Good Slowed by web-socket-js overhead.
Firefox 3.0.17 Fair Works fine but is slow.
Arora 0.5 Fair Slow due to broken putImageData and web-socket-js.
Opera 10.60 Poor web-socket-js problems, mouse/keyboard issues (see note 1)
Konqueror 4.2.2 Broken web-socket-js never loads

Windows XP

Browser Status Performance/Notes
Chrome 5.0.375.99 Excellent Very fast. Native WebSockets.
Safari 5.0 Excellent Fast. Native WebSockets.
Firefox 3.0.19 Good Some overhead from web-socket-js.
IE 6, 7, 8 Non-starter No basic Canvas support. Javascript painfully slow.

  • Note 1: Opera interacts poorly with web-socket-js. After two disconnects the browser tab or Flash often hang. Although Javascript is faster than Firefox 3.5, the high variability of web-socket-js performance results in overall performance being lower. Middle mouse clicks and keyboard events need some work to work properly under Opera. Also, Opera does not have support for setting the cursor style url to a data URI scheme, so cursor pseudo-encoding is disabled.

  • Note 2: Firefox 4.0 Beta does not provide a direct way to accept SSL certificates via WebSockets. You can work around this by navigating directly to the WebSockets port using 'https://' and accepting the certificate. Then return to noVNC and connect normally.

  • Note 3: Browsers using WebKit build 66396 through 68867 (Chrome/Chromium build 57968 through 61278) have a Canvas rendering bug. The WebKit bug is #46319. The noVNC bug is #28.