diff options
| author | rbyers@chromium.org <rbyers@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-14 20:28:06 +0000 |
|---|---|---|
| committer | rbyers@chromium.org <rbyers@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-14 20:28:06 +0000 |
| commit | 347a0c74816b8cea5e595e39dca62dd037b2d686 (patch) | |
| tree | c5289c11c8290696acb094bb98714c7a9b8a4a3d /ui/ui.gyp | |
| parent | aa26d4b3674c55cb189dc8081acdd1fbd272f4fe (diff) | |
| download | chromium_src-347a0c74816b8cea5e595e39dca62dd037b2d686.zip chromium_src-347a0c74816b8cea5e595e39dca62dd037b2d686.tar.gz chromium_src-347a0c74816b8cea5e595e39dca62dd037b2d686.tar.bz2 | |
Make touch-optimized-ui a tri-state flag
By default ('auto') touch-optimized-UI will be enabled if any touch screen is present. The user can also manually disable or enable it ('disabled', 'enabled') for testing purposes.
Note that for now --enable-touch-events is still required to enable the use of touch screens (and hence impact 'auto' here) since it's still experimental.
Also cleans up all the different ways we were trying to read this mode, unifying on ui::GetDisplayLayout().
BUG=124199
TBR=estade@chromium.org (only change in resources is trivial comment change)
TEST=
Review URL: https://chromiumcodereview.appspot.com/10391035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136968 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/ui.gyp')
| -rw-r--r-- | ui/ui.gyp | 2 |
1 files changed, 0 insertions, 2 deletions
@@ -240,8 +240,6 @@ 'base/theme_provider.h', 'base/touch/touch_factory.cc', 'base/touch/touch_factory.h', - 'base/touch/touch_mode_support.cc', - 'base/touch/touch_mode_support.h', 'base/ui_base_exports.cc', 'base/ui_base_paths.cc', 'base/ui_base_paths.h', |