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/test/app_remoting_connection_helper.cc b/remoting/test/app_remoting_connection_helper.cc
index 10daed0..39535f5 100644
--- a/remoting/test/app_remoting_connection_helper.cc
+++ b/remoting/test/app_remoting_connection_helper.cc
@@ -161,8 +161,8 @@
// Next send the host a description of the client screen size.
protocol::ClientResolution client_resolution;
- client_resolution.set_width(kDefaultWidth);
- client_resolution.set_height(kDefaultHeight);
+ client_resolution.set_width_deprecated(kDefaultWidth);
+ client_resolution.set_height_deprecated(kDefaultHeight);
client_resolution.set_x_dpi(kDefaultDPI);
client_resolution.set_y_dpi(kDefaultDPI);
client_resolution.set_dips_width(kDefaultWidth);
