diff options
| author | reillyg <reillyg@chromium.org> | 2015-01-07 22:44:34 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-01-08 06:45:27 +0000 |
| commit | 8a16c6beb41ac163dd7a05fe318b5bdd4102fb10 (patch) | |
| tree | 321c48464d6165abaab3b5843aec31d2bb7255c8 /chrome/browser/fullscreen_chromeos.cc | |
| parent | 2d2c3377a2f2154f62b69507f21aefc46cb29b95 (diff) | |
| download | chromium_src-8a16c6beb41ac163dd7a05fe318b5bdd4102fb10.zip chromium_src-8a16c6beb41ac163dd7a05fe318b5bdd4102fb10.tar.gz chromium_src-8a16c6beb41ac163dd7a05fe318b5bdd4102fb10.tar.bz2 | |
Remove the "Access your input devices" permission message.
As with the "Access your USB devices" permission message that was
removed in 400b26297782e70ed15e40d83b876e3abde7b9cc this permission
message duplicates the messages generated by the "usbDevices"
permission. I also consider it "overly alarmist" as the use case
for the chrome.hid API is often unrelated to input devices.
For example, the blink(1) sample app* has following single permission
string after this change, "Access any blink(1) from ThingM via USB."
* https://chrome.google.com/webstore/detail/kcpjgiicabigbjejdjnkflkdkjknkdch
BUG=
Review URL: https://codereview.chromium.org/840983002
Cr-Commit-Position: refs/heads/master@{#310458}
Diffstat (limited to 'chrome/browser/fullscreen_chromeos.cc')
0 files changed, 0 insertions, 0 deletions