If an app sends a CancelInteraction request for a speech-only Alert, the HMI responds with IGNORED and does not stop the current TTS. Also applies to SubtleAlert (note that as of now, TTS.Speak does not include a cancelID, so this could only really be correctly applied when the CancelInteraction request has no cancelID included)
Reproduction Steps
Send Alert with only ttsChunks included, TTS is started
Send CancelInteraction with functionID 12
Expected Behavior
TTS stops, app receives SUCCESS for CancelInteraction
Observed Behavior
TTS continues, app receives IGNORED for CancelInteraction
Browser & Version Information
Browser and Version: Google Chrome Version 97.0.4692.71
RPC Sent:
Alert ({"ttsChunks": {["text": "A long string of text to speak out loud", "type": "TEXT"]}})
CancelInteraction ({"functionID": 12})
Output Received: IGNORED, "The intended result is already in effect"
Bug Report
If an app sends a CancelInteraction request for a speech-only Alert, the HMI responds with IGNORED and does not stop the current TTS. Also applies to SubtleAlert (note that as of now, TTS.Speak does not include a cancelID, so this could only really be correctly applied when the CancelInteraction request has no cancelID included)
Reproduction Steps
Expected Behavior
TTS stops, app receives SUCCESS for CancelInteraction
Observed Behavior
TTS continues, app receives IGNORED for CancelInteraction
Browser & Version Information
{"ttsChunks": {["text": "A long string of text to speak out loud", "type": "TEXT"]}}) CancelInteraction ({"functionID": 12})