Update browser support to remove tables and be honest

Samuel Mannehed
2017-11-06 15:44:54 +01:00
parent 48b8145efb
commit 12587371b5

@@ -1,180 +1,16 @@
noVNC should work on any browser with reasonable HTML5 support.
In general this means:
noVNC should work on any modern browser with reasonable HTML5 support. Due to the fact that browser platforms are constantly updated and changed it is difficult to maintain a list of supported browsers the core noVNC team mainly test the newest versions of browsers. But the we *know* that versions older than the following **will not work**:
- Chrome 8
- Firefox 4
- Safari 6
- iOS Safari 5.1
- Opera 12
- iOS Safari 10
- Opera 12.1
- IE 11
- Edge 12
The major limiting factors are the HTML5 features Canvas, WebSockets
and Typed Arrays.
The older v0.1 release of noVNC has some support for older browsers
The old v0.1 release of noVNC has some support for older browsers
(e.g. Firefox 3.0, Chrome 4-7, Opera 10). Testing results for v0.1
can be found at [[Browser Support v0.1|Browser-support-0.1]].
The following tables show results of testing the current version of
noVNC on various browser and OS combinations.
### Ubuntu Maverick (10.10)
<table>
<tr>
<th>Browser</th>
<th>Status</th>
<th>Performance</th>
<th>Notes</th>
</tr> <tr>
<td>Chrome 13.0.782.220</td>
<td><b>Perfect</b></td>
<td><b>Very fast</b></td>
<td>Native WebSockets</td>
</tr> <tr>
<td>Firefox 7.0</td>
<td><b>Perfect</b></td>
<td><b>Very fast</b></td>
<td>Native WebSockets</td>
</tr> <tr>
<td>Firefox 6.0.2</td>
<td><b>Perfect</b></td>
<td><b>Very fast</b></td>
<td>Native WebSockets</td>
</tr> <tr>
<td>Firefox 4.0.1</td>
<td>Excellent</td>
<td>Fast</td>
<td>web-socket-js WebSocket emulation (see note 1)</td>
</tr> <tr>
<td>Firefox 3.6.18</td>
<td>Good</td>
<td>Moderate</td>
<td>web-socket-js WebSocket emulation (see note 1)</td>
</tr> <tr>
<td>Opera 11.51</td>
<td>Good</td>
<td>Moderate</td>
<td>WebSocket emulation with web-socket-js (see note 1)</td>
</tr> <tr>
<td>Opera 11.11</td>
<td>Good</td>
<td>Moderate</td>
<td>WebSocket emulation with web-socket-js (see note 1)</td>
</tr>
</table>
### Mobile Devices
<table>
<tr>
<th>Browser</th>
<th>Status</th>
<th>Performance</th>
<th>Notes</th>
</tr> <tr>
<td>iPad 2 (iOS 4.3.3)</td>
<td>Very Good</td>
<td>Moderate</td>
<td>Native WebSockets</td>
</tr> <tr>
<td>iPhone 3G (iOS 4.2.1)</td>
<td>Good</td>
<td>Slow</td>
<td>Native WebSockets</td>
</tr>
</table>
### Windows 7 (64-bit)
<table>
<tr>
<th>Browser</th>
<th>Status</th>
<th>Performance</th>
<th>Notes</th>
</tr> <tr>
<td>Chrome 14.0.835.186</td>
<td><b>Perfect</b></td>
<td>Fast</td>
<td>32-bit. Native WebSockets</td>
</tr> <tr>
<td>Firefox 7.0</td>
<td><b>Perfect</b></td>
<td>Fast</td>
<td>32-bit. Native WebSockets</td>
</tr> <tr>
<td>Opera 11.51</td>
<td><b>Perfect</b></td>
<td>Fast</td>
<td>32-bit. WebSocket emulation with web-socket-js</td>
</tr> <tr>
<td>Safari 5.1</td>
<td>Excellent</td>
<td>Fast</td>
<td>32-bit. Native WebSockets. Disconnect issues</td>
</tr> <tr>
<td>IE 9.0.8112.16421</td>
<td>Good</td>
<td>Fast</td>
<td>32-bit. WebSocket emulation with web-socket-js. Styling issues</td>
</tr> <tr>
<td>Firefox 6.0.2</td>
<td>Fair</td>
<td>Slow (note 3)</td>
<td>32-bit. Native WebSockets</td>
</tr>
</table>
### Windows XP
<table>
<tr>
<th>Browser</th>
<th>Status</th>
<th>Performance</th>
<th>Notes</th>
</tr> <tr>
<td>Chrome 14.0.835.186</td>
<td><b>Perfect</b></td>
<td><b>Very fast</b></td>
<td>Native WebSockets</td>
</tr> <tr>
<td>Firefox 6.0.2</td>
<td><b>Perfect</b></td>
<td>Fast</td>
<td>Native WebSockets</td>
</tr> <tr>
<td>Safari 5.0.2</td>
<td>Good</td>
<td>Moderate</td>
<td>Native WebSockets</td>
</tr> <tr>
<td>Firefox 3.6.15</td>
<td>Good</td>
<td>Moderate</td>
<td>WebSocket emulation with web-socket-js</td>
</tr>
</table>
* Note 1: Firefox 4/5 native WebSockets support can be enabled by
navigating to URL `about:config` and enabling option
`network.websocket.override-security-block`. Opera 11 native
WebSockets support can be enabled by browsing to URL
`opera:config#UserPrefs|EnableWebSockets` and enabling the option.
* Note 2: Firefox 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: Firefox 6 is abnormally slow running on Windows 7. I believe
this is a bug.
can be found at [[Browser Support v0.1|Browser-support-0.1]].