jcarr
/
noVNC
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

More browser table cleanup.

This commit is contained in:
Joel Martin 2010-07-02 12:40:29 -05:00
parent 47ef64634f
commit 3df41d67e1
1 changed files with 40 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

78
README.md
View File

@ -77,58 +77,60 @@ There a few reasons why a proxy is required:
### Browser Support ### Browser Support
In the following table Jaunty is Ubuntu 9.04 and WinXP is Windows XP.
#### Linux (Ubuntu 9.04) #### Linux (Ubuntu 9.04)
<table> <table>
<tr> <tr>
<th> OS </th> <th> Browser </th> <th>OS</th> <th>Browser</th>
<th> Status </th> <th>Status</th>
<th> Notes </th> <th>Notes</th>
</tr> <tr> </tr> <tr>
<td> Jaunty </td> <td> Chrome 5.0.375.29 </td> <td>Jaunty</td> <td>Chrome 5.0.375.29</td>
<td> Works great </td> <td>Excellent</td>
<td> Very fast. Native WebSockets. </td> <td>Very fast. Native WebSockets.</td>
</tr> <tr> </tr> <tr>
<td> Jaunty </td> <td> Firefox 3.5 </td> <td>Jaunty</td> <td> Firefox 3.5</td>
<td> Works well </td> <td>Good</td>
<td> Large full-color images are somewhat slow due to <td>Large full-color images are somewhat slow due to
web-socket-js overhead. </td> web-socket-js overhead.</td>
</tr> <tr> </tr> <tr>
<td> Jaunty </td> <td> Opera 10.60 </td> <td>Jaunty</td> <td> Opera 10.60</td>
<td> Works </td> <td>Fair</td>
<td> web-socket-js interaction makes it slower than firefox <td>web-socket-js interaction problems: slower than firefox,
and causes occasional hangs. </td> occasional hangs.</td>
</tr> <tr> </tr> <tr>
<td> Jaunty </td> <td> Arora 0.5 </td> <td>Jaunty</td> <td> Arora 0.5</td>
<td> Works </td> <td>Good</td>
<td> Broken putImageData so large full-color images <td>Broken putImageData so large full-color images
are slow. Uses web-socket-js. </td> are slow. Uses web-socket-js.</td>
</tr> <tr> </tr> <tr>
<td> Jaunty </td> <td> Konqueror 4.2.2 </td> <td>Jaunty</td> <td> Konqueror 4.2.2</td>
<td> <em>Broken</em> </td> <td><strong>Broken</strong></td>
<td> web-socket-js never loads </td> <td>web-socket-js never loads</td>
</tr> <tr> </tr> <tr>
<td> </td> <td></td>
<td> </td> <td></td>
<td> </td> <td></td>
<td> </td> <td></td>
</tr> <tr> </tr> <tr>
<td> WinXP </td> <td> Chrome 5.0.375.99 </td> <td>WinXP</td> <td> Chrome 5.0.375.99</td>
<td> Works great </td> <td>Excellent</td>
<td> Very fast. Native WebSockets. </td> <td>Very fast. Native WebSockets.</td>
</tr> <tr> </tr> <tr>
<td> WinXP </td> <td> Firefox 3.0.19 </td> <td>WinXP</td> <td> Firefox 3.0.19</td>
<td> Works well </td> <td>Good</td>
<td> Some overhead from web-socket-js. </td> <td>Some overhead from web-socket-js.</td>
</tr> <tr> </tr> <tr>
<td> WinXP </td> <td> Safari 5.0 </td> <td>WinXP</td> <td> Safari 5.0</td>
<td> Works </td> <td>Fair</td>
<td> Fast. Native WebSockets. Broken 'wss://' <td>Fast. Native WebSockets. Broken 'wss://'
(SSL) - weird client header </td> (SSL) - weird client header</td>
</tr> <tr> </tr> <tr>
<td> WinXP </td> <td> IE 6, 7, 8</td> <td>WinXP</td> <td> IE 6, 7, 8</td>
<td> <em>Non-starter</em> </td> <td><strong>Non-starter</strong></td>
<td> No basic Canvas support. Javascript painfully slow. </td> <td>No basic Canvas support. Javascript painfully slow.</td>
</tr> </tr>
</table> </table>