Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Bug report: Firefox Reader TTS (Narrate): Stops at each line break ('\n')

  • 1 reply
  • 1 has this problem
  • 6 views
  • Last reply by ssmid

ssmid
ssmid
more options

First of all: I could not find any article on how to file a bug report, so I opened up this question.

The built-in TTS function "Narrate" stops reading for a second, whenever a line break ('\n') occurs. Unfortunately, in my case (https://paroj.github.io/gltut/About%20this%20Book.html), there are lots of line breaks in the middle of the text, making using Narrate impossible.

(You can find the TTS function if you open up the Reader in the URL bar, in case you want to reproduce this.)

Is there anything I can do to fix this? (besides trying to do a browser extension)

Thanks

First of all: I could not find any article on how to file a bug report, so I opened up this question. The built-in TTS function "Narrate" stops reading for a second, whenever a line break ('\n') occurs. Unfortunately, in my case (https://paroj.github.io/gltut/About%20this%20Book.html), there are lots of line breaks in the middle of the text, making using Narrate impossible. (You can find the TTS function if you open up the Reader in the URL bar, in case you want to reproduce this.) Is there anything I can do to fix this? (besides trying to do a browser extension) Thanks

All Replies (1)

ssmid
ssmid Question owner
more options

Using my advanced web search skills, I managed to write this probably horrible JS code:

Javascript function ttsWorkaround() { 

 var paragraphs = document.getElementsByTagName('p');
 for (let p of paragraphs) {
   p.innerHTML = p.innerHTML.replace(/\n */g, ' ');
 }

}

ttsWorkaround();

To apply this to every book/web page without using the console, one probably has to write an extension. And one might want to change the name of the tag ('p') to whatever tag fits the specific page. (Maybe even 'body'.)