Parse media keys for named command in the manifest.

chrome/common/extensions/docs/examples/api/mediaKeysCommand/manifest.json

+{
+  "name": "MediaKeys",
+  "description": "Sample Extension Commands extension For Media Keys",
+  "version": "1.0",
+  "manifest_version": 2,
+  "background": {
+    "scripts": ["background.js"],
+    "persistent": false
+  },
+  "browser_action": {
+    "default_popup": "browser_action.html"
+  },
+  "commands": {
+    "next-track": {
+      "suggested_key": {
+        "default": "MediaNextTrack"
+      },
+      "description": "Media next track"
+    },
+    "prev": {
+      "suggested_key": {
+        "default": "MediaPrevTrack"
+      },
+      "description": "Media previous track"
+    },
+    "play-pause": {
+      "suggested_key": {
+        "default": "MediaPlayPause"
+      },
+      "description": "Media play/pause"
+    },
+    "stop": {
+      "suggested_key": {
+        "default": "MediaStop"
+      },
+      "description": "Media stop"
+    }
+  }
+}

[Finnur, 2013/08/28 14:15:16]

I don't think this sample is needed, but if so, there are a few issues with it:
1) There's no mediaKeys API (as the path for this doc indicates). Media Key
support will be tucked into the Commands API and we already have an example for
the Commands API, so this doesn't add much.
2) There's a browser action in this sample that is not needed.

However, I was expecting a corresponding change to the Commands API doc that
explains that you can now listen for some of the Media keys.
See: 
chrome\common\extensions\docs\templates\intros\commands.html

... unless we mean to not support Media keys with non-global shortcuts (then we
keep the docs as-is). I don't know which makes sense, but I'll ask the PM.

[zhchbin, 2013/08/29 06:20:14]

Removal of example: Done.
Doc commands API doc: I would like to add it after this cl? Because currently I
can only make sure it works fine on Windows platform.

[Finnur, 2013/08/29 11:20:52]

Fine.