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..e274c0dad9d7f98e72acaaf948e59f0c5a200b6e 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 leave the paused state." |
David Tseng
2013/05/20 17:39:51
Is this true? The tts controller continues to have
|
+ }, |
+ { |
+ "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 also implies resuming." |
not at google - send to devlin
2013/05/13 14:46:53
What does "implies" mean? That the extension shou
dmazzoni
2013/05/14 16:50:27
Clarified: the extension should exit the paused st
|
} |
] |
} |