diff options
| author | derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-09 20:32:18 +0000 |
|---|---|---|
| committer | derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-09 20:32:18 +0000 |
| commit | 16f3e30d213bd3708591d6a513889e395c485ac8 (patch) | |
| tree | 2bdf875eb28b8ecdb6f79cd2600799cad5502376 /gpu/command_buffer/service/feature_info.h | |
| parent | c6f57f9e22339c7beb608a67ac9bb90425ed84e6 (diff) | |
| download | chromium_src-16f3e30d213bd3708591d6a513889e395c485ac8.zip chromium_src-16f3e30d213bd3708591d6a513889e395c485ac8.tar.gz chromium_src-16f3e30d213bd3708591d6a513889e395c485ac8.tar.bz2 | |
chromeos: Request screen lock directly from session manager.
Screen lock and unlock requests were previously sent to
powerd, which just forwarded them on to the session manager
without doing anything extra. It's simpler for Chrome to
just ask the session manager to lock or unlock directly.
I'm also moving the LockScreen and UnlockScreen
notifications from PowerManagerClient::Observer to
SessionManagerClient::Observer. Confusingly, the signals
that prompt those notifications are sent by the session
manager but were being listened for in PowerManagerClient.
BUG=chromium-os:24003
TEST=manual: able to lock the screen from the UI, power button, and by closing the lid; unlocking works too
Review URL: https://chromiumcodereview.appspot.com/10693087
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145737 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gpu/command_buffer/service/feature_info.h')
0 files changed, 0 insertions, 0 deletions