diff options
| author | qfel@google.com <qfel@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-30 17:09:32 +0000 |
|---|---|---|
| committer | qfel@google.com <qfel@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-30 17:09:32 +0000 |
| commit | b1186477901883f22ae9e3d0c0266557735a062e (patch) | |
| tree | 9e4d0e87c83f7911fd51ce6c7d1a683a6d90e2dc /third_party/libevent/aclocal.m4 | |
| parent | 9e00e635121e693b18dc0d5e9b973753febe111d (diff) | |
| download | chromium_src-b1186477901883f22ae9e3d0c0266557735a062e.zip chromium_src-b1186477901883f22ae9e3d0c0266557735a062e.tar.gz chromium_src-b1186477901883f22ae9e3d0c0266557735a062e.tar.bz2 | |
Screenshot disabling policy (work in progress)
Add group policy to disable taking screenshots:
* by keyboard shortcut (using local state)
* when reporting feedback (using local state)
* by extension API (using user prefs)
How to test:
- Press Ctrl+F5 (or the corresponding key combination on chromebook) to take a screenshot. This should flash a screen and create a screenshot in your files, if the policy is not enabled.
- Install http://code.google.com/chrome/extensions/examples/api/tabs/screenshot.zip extension to test extension APIs. This allows to take tab screenshots of code.google.com.
- In Chrome menu, use Tools -> Report an Issue... to go to issue screen, which should contain a screenshot (if the policy is not enabled)
Implementation:
- Changed browser::GrabWindowSnapshot and ScreenshotTaker::GrabWindowSnapshot to block screenshots triggered by accelerators and feedback form
- CaptureVisibleTabFunction::RunImpl to disable tab screenshots made by extension API
BUG= chromium-os:24747
TEST= Disable screenshots through policy, check I screenshots can created/viewed
TBR= zmo@chromium.org, jbates@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10692110
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148963 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/libevent/aclocal.m4')
0 files changed, 0 insertions, 0 deletions