Add Pause and Resume to Web TTS & Extension TTS APIs

chrome/common/extensions/api/tts_engine.json

Index: chrome/common/extensions/api/tts_engine.json
diff --git a/chrome/common/extensions/api/tts_engine.json b/chrome/common/extensions/api/tts_engine.json
index 30b33fcfe32a21eef7cd02e51f0eae8c2d756624..35b064d94f6b9d10ff9c0d0edf1949a20907ce99 100644
--- a/chrome/common/extensions/api/tts_engine.json
+++ b/chrome/common/extensions/api/tts_engine.json
@@ -97,6 +97,16 @@
         "name": "onStop",
         "type": "function",
         "description": "Fired when a call is made to tts.stop and this extension may be in the middle of speaking. If an extension receives a call to onStop and speech is already stopped, it should do nothing (not raise an error)."
+      },
+      {
+        "name": "onPause",
+        "type": "function",
+        "description": "Optional: if an engine supports the pause event, it should pause the current utterance being spoken, if any, until a resume, stop, or speak event is fired, all of which should clear the paused state."

[David Tseng, 2013/05/21 16:50:41]

In light of the other comment, shouldn't the engine always receive resume before
receiving a speak event? (i.e. remove speak from the list above).

[dmazzoni, 2013/05/28 07:37:31]

Agreed.

After thinking about this some more, the current code will never tell and engine
to Start
while it's in the Paused state. After a Pause, it will only get either a Resume
or a Stop.
Clarified the comment to indicate that either Resume or Stop should clear the
paused
state.

+      },
+      {
+        "name": "onResume",
+        "type": "function",
+        "description": "Optional: if an engine supports the pause event, it should also support the resume event, to continue speaking the current utterance, if any. Note that a stop or speak event should also clear the paused state."
       }
     ]
   }