Don't allow "touch optimized ui" mode to change after chrome startup.
Since we don't yet properly support dynamic changing of touch optimized UI mode (see crbug.com/124399), we need to ensure the UI sees a consistent value for the life of the process to avoid painting issues like those in issue 131606.
Also output a log message if we see touch device status change after startup in order to help understand issues with some devices being slow to initialize.
Adds a temporary hack to force touch-optimized-ui mode on when command line arguments suggest we're expecting a touch screen.
BUG=131606
TEST=
Review URL: https://chromiumcodereview.appspot.com/10532161
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142493 0039d316-1c4b-4281-b951-d872f2087c98
3 files changed
