Move the tts and ttsEngine APIs out of experimental, and give

chrome/common/extensions/extension_permission_set.cc

Index: chrome/common/extensions/extension_permission_set.cc
===================================================================
--- chrome/common/extensions/extension_permission_set.cc	(revision 92693)
+++ chrome/common/extensions/extension_permission_set.cc	(working copy)
@@ -299,6 +299,14 @@
       IDS_EXTENSION_PROMPT_WARNING_TABS,
       ExtensionPermissionMessage::kTabs);
   RegisterExtensionPermission(
+      ExtensionAPIPermission::kTts, "tts",
+      IDS_EXTENSION_PROMPT_WARNING_TTS,

[Erik does not do reviews, 2011/07/15 23:04:04]

Do we really need a TTS warning?  My take is that this falls into the
"annoyance" category like notifications and quota that we don't warn for.

[dmazzoni, 2011/07/20 05:58:04]

Done.

+      ExtensionPermissionMessage::kTts);
+  RegisterExtensionPermission(
+      ExtensionAPIPermission::kTtsEngine, "ttsEngine",
+      IDS_EXTENSION_PROMPT_WARNING_TTS_ENGINE,

[Erik does not do reviews, 2011/07/15 23:04:04]

This one seems fine though.

+      ExtensionPermissionMessage::kTtsEngine);
+  RegisterExtensionPermission(
       ExtensionAPIPermission::kWebSocketProxyPrivate,
       "webSocketProxyPrivate", 0,
       ExtensionPermissionMessage::kNone);