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

Proper error handling for tight filters 

Don't throw an exception when we encounter an unsupported tight
subencoding.
This commit is contained in:
samhed 2016-06-10 17:15:42 +02:00
parent 3daa86cbae
commit b2cdd55859
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
include/rfb.js
View File

@ -2011,8 +2011,7 @@ var RFB;
} else { } else {
// Filter 0, Copy could be valid here, but servers don't send it as an explicit filter // Filter 0, Copy could be valid here, but servers don't send it as an explicit filter
// Filter 2, Gradient is valid but not use if jpeg is enabled // Filter 2, Gradient is valid but not use if jpeg is enabled
// TODO(directxman12): why aren't we just calling '_fail' here this._fail("Unsupported tight subencoding received, filter: " + filterId);
throw new Error("Unsupported tight subencoding received, filter: " + filterId);
} }
break; break;
case "copy": case "copy":