Open
Bug 1412826
Opened 8 years ago
Updated 3 years ago
Web Speech can't be restarted
Categories
(Core :: Web Speech, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: winstonma, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36
Steps to reproduce:
1. Go to https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/speechsynthesis/
2. On the textbox, enter "Hello World"
3. Press the "Speak" button at the bottom
4. Wait until the speech finishes
5. Press the "Speak" button again
6. Hear no voice
Actual results:
Speak "hello world" once and then nothing happens
I tried this on Firefox 56 and Firefox 58. It is being fixed on Firefox 58 but I am not sure if it happens on upcoming release of Firefox.
Expected results:
It should speak "hello world" whenever we press the "speak" button.
I tried on Safari as well as Chrome, the browser will speak again "hello world" whenever I press the "speak" button.
Works for me in Fx56.0.2, 57b12 and Nightly 58 (all in x64) on Win10 RS3.
Has STR: --- → yes
Component: Untriaged → Web Speech
Product: Firefox → Core
Comment 3•8 years ago
|
||
I believe that this is fixed by bug 1406358 (root cause is same). and Wiston says, "It is being fixed on Firefox 58". Do you want fix on 56 or 57?
Flags: needinfo?(winstonma)
Makoto, I just ran FF57b13 and could confirm that TTS repeat is not working. I guess you are right, the root cause is the same.
Initially I thought they are different set of codebase because the CPU loading on the web page is much lower than in Reader Mode. Then I think the CPU loading issue is only on Reader Mode.
I am just reporting bug as it is not working. I think it is better to leave it to you guys to make the call. Just to mention FF58 will be released on Jan 2018.
Flags: needinfo?(winstonma)
Comment 5•8 years ago
|
||
(In reply to Winston from comment #4)
> Makoto, I just ran FF57b13 and could confirm that TTS repeat is not working.
> I guess you are right, the root cause is the same.
>
> Initially I thought they are different set of codebase because the CPU
> loading on the web page is much lower than in Reader Mode. Then I think the
> CPU loading issue is only on Reader Mode.
>
> I am just reporting bug as it is not working. I think it is better to leave
> it to you guys to make the call. Just to mention FF58 will be released on
> Jan 2018.
I am already requesting uplift for 57 (bug 1406358 comment #18)
As Makoto mentioned, this issue is caused by bug 1406358.
I also checked that this issue no longer exist in the latest version, so I guess this ticket can be closed.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•