Add flag to experiments to force high DPI mode.

Add flag to experiments to force high DPI mode.

This adds --default-device-scale-factor to flags and makes this flag override the aura monitor scale factor and forces enable_viewport on web contents.

BUG=124412
TEST=When flag is enabled, web contents are drawn at 2x and aura monitor scale factor is set to 2x.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=134741

[flackr, 2012-04-27 18:15:54]

Hi guys, this change makes default-device-scale-factor the one-stop flag for
testing other scale factors and adds the 2x version to chrome://flags. Using
this instead of --aura-host-window-size allows us to change the scale factor
independent of the screen resolution and will probably be a nice test flag for
high DPI. PTAL, thanks!

[sky, 2012-04-27 19:44:45]

LGTM

http://codereview.chromium.org/10254011/diff/1/ui/aura/monitor_manager.cc
File ui/aura/monitor_manager.cc (right):

http://codereview.chromium.org/10254011/diff/1/ui/aura/monitor_manager.cc#new...
ui/aura/monitor_manager.cc:52:
base::StringToInt(CommandLine::ForCurrentProcess()->GetSwitchValueASCII(
check return value.

[flackr, 2012-04-30 14:05:15]

http://codereview.chromium.org/10254011/diff/1/ui/aura/monitor_manager.cc
File ui/aura/monitor_manager.cc (right):

http://codereview.chromium.org/10254011/diff/1/ui/aura/monitor_manager.cc#new...
ui/aura/monitor_manager.cc:52:
base::StringToInt(CommandLine::ForCurrentProcess()->GetSwitchValueASCII(
On 2012/04/27 19:44:46, sky wrote:
> check return value.

Done.

[oshima, 2012-04-30 17:46:18]

lgtm

FYI:  http://codereview.chromium.org/10255020/

[commit-bot: I haz the power, 2012-04-30 23:39:25]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/flackr@chromium.org/10254011/4002

[commit-bot: I haz the power, 2012-04-30 23:39:28]

Can't apply patch for file chrome/browser/about_flags.cc.
While running patch -p1 --forward --force;
patching file chrome/browser/about_flags.cc
Hunk #1 FAILED at 663.
1 out of 1 hunk FAILED -- saving rejects to file
chrome/browser/about_flags.cc.rej

[commit-bot: I haz the power, 2012-05-01 00:01:14]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/flackr@chromium.org/10254011/6003

[commit-bot: I haz the power, 2012-05-01 00:01:42]

Presubmit check for 10254011-6003 failed and returned exit status 1.

Running presubmit commit checks ...

** Presubmit ERRORS **
Missing LGTM from an OWNER for files in these directories:
    content/renderer

Presubmit checks took 5.2s to calculate.

Was the presubmit check useful? Please send feedback & hate mail to
maruel@chromium.org!

[flackr, 2012-05-01 00:42:54]

+piman, for content/renderer. PTAL, thanks!

[piman, 2012-05-01 00:48:50]

lgtm

[commit-bot: I haz the power, 2012-05-01 01:06:21]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/flackr@chromium.org/10254011/6003

[commit-bot: I haz the power, 2012-05-01 01:35:39]

Try job failure for 10254011-6003 (retry) on linux_chromeos for step "compile"
(clobber build).
It's a second try, previously, step "compile" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

[commit-bot: I haz the power, 2012-05-01 16:32:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/flackr@chromium.org/10254011/6003

[commit-bot: I haz the power, 2012-05-01 17:20:43]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/flackr@chromium.org/10254011/10003

[commit-bot: I haz the power, 2012-05-01 19:02:27]

Change committed as 134741