Fix logic handling empty strings in tts.

chrome/browser/resources/chromeos/chromevox/host/chrome/tts_background.js

Index: chrome/browser/resources/chromeos/chromevox/host/chrome/tts_background.js
diff --git a/chrome/browser/resources/chromeos/chromevox/host/chrome/tts_background.js b/chrome/browser/resources/chromeos/chromevox/host/chrome/tts_background.js
index 94376942a4745dbc7a8f5d386bfe57119d2cd52c..b972aa059b7f9775f3b14ce2f0726d4d3885daab 100644
--- a/chrome/browser/resources/chromeos/chromevox/host/chrome/tts_background.js
+++ b/chrome/browser/resources/chromeos/chromevox/host/chrome/tts_background.js
@@ -257,6 +257,8 @@ cvox.TtsBackground.prototype.speak = function(
   // any speech very well. Handle empty and whitespace only strings (including
   // non-breaking space) here to mitigate the issue somewhat.
   if (/^[\s\u00a0]*$/.test(textString)) {
+    queueMode = cvox.QueueMode.FLUSH;
+
     // We still want to callback for listeners in our content script.
     if (properties['startCallback']) {
       try {
@@ -270,9 +272,6 @@ cvox.TtsBackground.prototype.speak = function(
       } catch (e) {
       }
     }
-    if (queueMode === cvox.QueueMode.FLUSH) {
-      this.stop();
-    }
     return this;
   }