The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484

commit d02d32f9400a58ea0c9e5beb1ecc25f5beefe484
Author: riajiang <riajiang@chromium.org>
Date: Wed Dec 21 21:34:13 2016

Scale bounds in aura-mus client-lib and NativeWidgetMus in hdpi mode.

Also use the correct device scale factor in WindowTreeHostMus.

BUG= 646942 
TEST=manual (with --force-device-scale-factor=2)

Review-Url: https://codereview.chromium.org/2579883002
Cr-Commit-Position: refs/heads/master@{#440224}

[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_port_mus.cc
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_port_mus.h
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_tree_client.cc
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_tree_client.h
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_tree_client_unittest.cc
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_tree_host_mus.cc
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/aura/mus/window_tree_host_mus.h
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/views/mus/native_widget_mus.cc
[modify] https://crrev.com/d02d32f9400a58ea0c9e5beb1ecc25f5beefe484/ui/views/mus/native_widget_mus.h

Tested this issue on Mac 10.12.2 using Chrome Version#57.0.2970.0 with the below steps:

1.Launched chrome with flag "--force-device-scale-factor=2"  & observed chrome lunched successfully with flag
2.Navigate to new tab
3.Right click & observed context menu.

Please find the attached screencast & confirm the expected behaviour for the same.

Also please confirm this issue is specific to Chrome OS or for all OS (Windows,Mac & Linux)?

Thanks in advance.

Deleted: 646942.mp4 3.0 MB

	646942.mp4 3.0 MB View Download

Window bounds is working correctly in non-mash mode (without --mash flag). All these changes are not being used yet.

Indeed. These changes are not active yet. Also, this would initially affect only ChromeOS. Updating the OS list in the bug to reflect that.