Update permission bubble strings with contextual verbs

Update permission bubble strings with contextual verbs

BUG=468600
R=meacer@chromium.org

Committed: https://crrev.com/a9e0c0d8c6e22f0408bd5893f0978066df3de516
Cr-Commit-Position: refs/heads/master@{#323859}

[felt, 2015-03-31 10:31:41]

meacer, ptal

[meacer, 2015-03-31 18:10:40]

https://codereview.chromium.org/1050453002/diff/1/chrome/app/generated_resour...
File chrome/app/generated_resources.grd (right):

https://codereview.chromium.org/1050453002/diff/1/chrome/app/generated_resour...
chrome/app/generated_resources.grd:13053: +          Send notifications
Shouldn't this be "Show notifications" instead?

https://codereview.chromium.org/1050453002/diff/1/chrome/app/generated_resour...
chrome/app/generated_resources.grd:13490: +        Know your location
Extension strings use "detect your physical location". Would be good to make
them consistent. (I'm not necessarily suggesting to change this one)

https://codereview.chromium.org/1050453002/diff/1/chrome/app/generated_resour...
chrome/app/generated_resources.grd:13552: +        Play sound on MIDI devices
My understanding is that MIDI permission is only required for privileged MIDI
operations which give exclusive control to MIDI devices (via sysex parameter):
http://webaudio.github.io/web-midi-api/#security-and-privacy-considerations-o...

This goes beyond simply playing sound and includes things like enumerating
devices, reading input (such as knobs) and sending output that don't always
result in sound. In contrast, playing simple sounds doesn't require sysex access
so won't result in a prompt.

Given that, I think we should make this warning more accurate. Perhaps something
like "Have full access to MIDI devices"? It would be less user friendly, but
similar USB or Bluetooth: If you don't know what USB is, you probably shouldn't
give USB access to the webpage.

https://codereview.chromium.org/1050453002/diff/1/chrome/app/generated_resour...
chrome/app/generated_resources.grd:13616: +          Access your protected
content identifier
There is an extension permission similar to this which reads "Read a unique
identifier for this computer". I hoped that would translate better than
"protected identifier", but no, its TR localization is still horrible :/

[meacer, 2015-03-31 21:42:36]

And I now realize you already mentioned MIDI and content identifier in the bug.

[felt, 2015-03-31 21:43:50]

On 2015/03/31 21:42:36, Mustafa Emre Acer wrote:
> And I now realize you already mentioned MIDI and content identifier in the
bug.

I'm going to stick with whatever rolfe@ tells me the strings should be, but feel
free to leave comments on the bug if you disagree with the UI strings. I'll wait
for what she says about MIDI and content identifier.

[felt, 2015-04-03 04:01:33]

I update the strings per the discussion on the bug

[meacer, 2015-04-03 17:51:36]

On 2015/04/03 04:01:33, felt wrote:
> I update the strings per the discussion on the bug

LGTM, though I still have concerns about "Send notifications" as I mentioned in
the bug.

[felt, 2015-04-03 23:08:45]

The CQ bit was checked by felt@chromium.org

[commit-bot: I haz the power, 2015-04-03 23:09:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1050453002/20001

[commit-bot: I haz the power, 2015-04-04 00:34:04]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-04-04 00:35:17]

Patchset 2 (id:??) landed as
https://crrev.com/a9e0c0d8c6e22f0408bd5893f0978066df3de516
Cr-Commit-Position: refs/heads/master@{#323859}