Fix event dispatching and window resizing in high-dpi mode.

ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc

Index: ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc
diff --git a/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc b/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc
index 816faa3f312f4ef52ff418a99b5e3d7016ac760c..3d3380dd4a372f90e610ae835883b3f157527e05 100644
--- a/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc
+++ b/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc
@@ -1801,6 +1801,7 @@ void DesktopWindowTreeHostX11::ConvertEventToDifferentHost(
   gfx::PointF location_in_pixel_in_host =
       located_event->location_f() + gfx::Vector2dF(offset);
   located_event->set_location_f(location_in_pixel_in_host);
+  located_event->set_root_location_f(location_in_pixel_in_host);

[rjkroege, 2016/10/10 20:49:31]

is set_root_location_f in DIP or DDP? In screen space? event.h doesn't say. But
probably should (maybe in a different CL?)

[sadrul, 2016/10/11 15:13:37]

crbug.com/608547 is for this specific case, to replace 'root location' with a
'system location', and better define what exactly it means. For now,
unfortunately, this 'root location' can be in physical pixel space in some
places (e.g. immediately when the event is created from a native event), and in
DIP in other places (e.g. during the dispatch phase). So there isn't a good way
to clarify this with a comment in event.h

In this specific case, however, the event location is in physical pixel space
(which is why the local var-name has '_in_pixel_' in it)

 }
 
 void DesktopWindowTreeHostX11::ResetWindowRegion() {