summaryrefslogtreecommitdiffstats
path: root/chrome/chrome_browser.gypi
diff options
context:
space:
mode:
authorscherkus@chromium.org <scherkus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-05-17 21:04:02 +0000
committerscherkus@chromium.org <scherkus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-05-17 21:04:02 +0000
commitcc4c974335ecf328de5a22e9e75254397f18702e (patch)
tree2686fcc00a58973a9700edca1b11d1762e1018c4 /chrome/chrome_browser.gypi
parentdd963e61f462ae0ec47d5d559d6b52f6219a9c19 (diff)
downloadchromium_src-cc4c974335ecf328de5a22e9e75254397f18702e.zip
chromium_src-cc4c974335ecf328de5a22e9e75254397f18702e.tar.gz
chromium_src-cc4c974335ecf328de5a22e9e75254397f18702e.tar.bz2
Handling volume up/down/mute keypresses within Chrome.
When Window Manager sends us a NOTIFY_SYSKEY_CLICKED message, we adjust the volume accordingly. Currently just calling amixer as WM was doing before. There will be a different change submitted for WM to send this message instead of calling amixer itself. Patch by davej@chromium.org: http://codereview.chromium.org/2102001/show BUG=cros/525 TEST=none Related to issue 2107001. Review URL: http://codereview.chromium.org/2107010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47451 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_browser.gypi')
-rw-r--r--chrome/chrome_browser.gypi2
1 files changed, 2 insertions, 0 deletions
diff --git a/chrome/chrome_browser.gypi b/chrome/chrome_browser.gypi
index f741231..745952d 100644
--- a/chrome/chrome_browser.gypi
+++ b/chrome/chrome_browser.gypi
@@ -500,6 +500,8 @@
'browser/chromeos/status/status_area_host.h',
'browser/chromeos/status/status_area_view.cc',
'browser/chromeos/status/status_area_view.h',
+ 'browser/chromeos/system_key_event_listener.cc',
+ 'browser/chromeos/system_key_event_listener.h',
'browser/chromeos/usb_mount_observer.cc',
'browser/chromeos/usb_mount_observer.h',
'browser/chromeos/version_loader.cc',