Skip to content

Commit

Permalink
Proper error handling for tight filters
Browse files Browse the repository at this point in the history
Don't throw an exception when we encounter an unsupported tight
subencoding.
  • Loading branch information
samhed committed Jun 10, 2016
1 parent 3daa86c commit b2cdd55
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions include/rfb.js
Original file line number Diff line number Diff line change
Expand Up @@ -2011,8 +2011,7 @@ var RFB;
} else {
// 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
// TODO(directxman12): why aren't we just calling '_fail' here
throw new Error("Unsupported tight subencoding received, filter: " + filterId);
this._fail("Unsupported tight subencoding received, filter: " + filterId);
}
break;
case "copy":
Expand Down

0 comments on commit b2cdd55

Please sign in to comment.