Hide the cursor on the client when it is hidden on the host

remoting/protocol/client_control_dispatcher.cc

Index: remoting/protocol/client_control_dispatcher.cc
diff --git a/remoting/protocol/client_control_dispatcher.cc b/remoting/protocol/client_control_dispatcher.cc
index 599c779fbae4a3e4ea21f86e41c24a23d99221db..5a6bad59f49bf1019b53869ec19c11217eceaad2 100644
--- a/remoting/protocol/client_control_dispatcher.cc
+++ b/remoting/protocol/client_control_dispatcher.cc
@@ -38,8 +38,8 @@ bool CursorShapeIsValid(const CursorShapeInfo& cursor_shape) {
 
   // Verify that |width| and |height| are within sane limits. Otherwise integer
   // overflow can occur while calculating |cursor_total_bytes| below.
-  if (width <= 0 || width > (SHRT_MAX / 2) ||
-      height <= 0 || height > (SHRT_MAX / 2)) {
+  if (width < 0 || width > (SHRT_MAX / 2) ||
+      height < 0 || height > (SHRT_MAX / 2)) {

[Wez, 2015/01/06 23:24:25]

Since you're making this change in the client-side control channel dispatcher,
it won't "go live" until either we switch over entirely to the v2 app, or this
change makes it into Chrome.

Are we already hitting this when other hosts see empty cursors?

     LOG(ERROR) << "Cursor dimensions are out of bounds for SetCursor: "
                << width << "x" << height;
     return false;