summaryrefslogtreecommitdiffstats
path: root/build/common.gypi
diff options
context:
space:
mode:
authorderat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-03-14 17:45:08 +0000
committerderat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-03-14 17:45:08 +0000
commitf8846c017b91f6a383d1c708a181e7cbda43baa5 (patch)
tree0e6aeefb0b95a142c695d437d5db263492863262 /build/common.gypi
parentc83e4af2965e0c173a45ffe93a75cc4ab5eb29a2 (diff)
downloadchromium_src-f8846c017b91f6a383d1c708a181e7cbda43baa5.zip
chromium_src-f8846c017b91f6a383d1c708a181e7cbda43baa5.tar.gz
chromium_src-f8846c017b91f6a383d1c708a181e7cbda43baa5.tar.bz2
chromeos: Avoid showing brightness bubble for auto changes.
This change updates Chrome to use the new libcros brightness-monitoring interface from http://codereview.chromium.org/6625027/ so that we can animate the brightness bubble's level in response to automatic changes initiated by the power manager, but avoid showing the bubble onscreen unless it's already visible from an earlier user-initiated change. I'm also changing the libcros dependency to ccea53b3 to pick up the new interface. BUG=chromium-os:12645 TEST=built and ran on a device with my powerd and libcros changes; manually tested that the bubble behaves as expected with various combinations of plugging/unplugging AC and hitting the brightness buttons Review URL: http://codereview.chromium.org/6658023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78051 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/common.gypi')
0 files changed, 0 insertions, 0 deletions