Use only DIPs size in ClientResolution.
ClientResolution message contains DIPs and device size fields. DIPs
size was marked as legacy, but it was actually used by the host. It's
best to use DIPs for consistency with other messages, particularly
VideoTrackLayout. marked device-pixel size as deprecated and the host
now works when width/height fields are not specified.
Review-Url: https://codereview.chromium.org/2021773002
Cr-Commit-Position: refs/heads/master@{#397102}
diff --git a/remoting/proto/control.proto b/remoting/proto/control.proto
index f6922f1..72c843d 100644
--- a/remoting/proto/control.proto
+++ b/remoting/proto/control.proto
@@ -11,13 +11,13 @@
package remoting.protocol;
message ClientResolution {
- // Legacy width and height of the client in Density-Independent Pixels
+ // Width and height of the client in Density-Independent Pixels
optional int32 dips_width = 1;
optional int32 dips_height = 2;
- // Width and height of the client in device pixels.
- optional int32 width = 3;
- optional int32 height = 4;
+ // Deprecated width and height of the client in device pixels.
+ optional int32 width_deprecated = 3;
+ optional int32 height_deprecated = 4;
// Horizontal and vertical DPI of the screen. If either of these is zero or
// unset, the corresponding DPI should be assumed to be 96 (Windows' default)
