Issue 131734 in chromium: Add switch and flags page to enable accelerator to switch device scale factor on chromeos

[chro...@googlecode.com]

Status: Assigned
Owner: tha...@chromium.org
Labels: Type-Bug Pri-2 Area-UI OS-Chrome Feature-Ash-DIP

New issue 131734 by osh...@chromium.org: Add switch and flags page to
enable accelerator to switch device scale factor on chromeos
http://code.google.com/p/chromium/issues/detail?id=131734

The accelerator exists but it's currently excluded from release build.

The accelerator command is MONITOR_TOGGLE_SCALE and key binding is
ctrl-shift-home. You can find it in

ash/accelerators/accelerator_controller.cc
ash/accelerators/accelerator_table.cc

[chro...@googlecode.com]

Updates:
Cc: rjkr...@chromium.org osh...@chromium.org
Labels: Hotlist-Link MStone-22

Comment #1 on issue 131734 by rby...@chromium.org: Add switch and flags

page to enable accelerator to switch device scale factor on chromeos
http://code.google.com/p/chromium/issues/detail?id=131734

This is just for testing/development purposes, right? Today you can test
high-DPI on ChromeOS with the force flag in about:flags, but the only way
to test dynamic switching is with 2 monitors, one of which actually reports
high-dpi.

I can imagine some website JavaScript could be broken in the face of
dynamic switching, so we probably should make sure there's an easy way to
test on ChromeOS.

[chro...@googlecode.com]

Comment #2 on issue 131734 by tha...@chromium.org: Add switch and flags

page to enable accelerator to switch device scale factor on chromeos
http://code.google.com/p/chromium/issues/detail?id=131734

about:flags can't do dynamic switching, as changing flags requires chrome
restarts. You're saying there's already something in about:flags to turn on
hidpi? Because that's what this bug is for.

[chro...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 124412

Comment #3 on issue 131734 by tha...@chromium.org: Add switch and flags

page to enable accelerator to switch device scale factor on chromeos
http://code.google.com/p/chromium/issues/detail?id=131734

Looks like this is done already :-)