Closed Bug 1234654 Opened 9 years ago Closed 10 months ago

WebSpeech stops working

Categories

(Core :: Web Speech, defect)

46 Branch
x86
Windows 8.1
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: kolan_n, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20151222030207

Steps to reproduce:

When incorrect or missing SAPI language ID is provided, for example
speechSynthesis.speak(new SpeechSynthesisUtterance('<voice required="Language=ololo">ololo</voice>'))


Actual results:

WebSpeech stops working


Expected results:

it mustn't
Component: Untriaged → Web Speech
OS: Unspecified → Windows 8.1
Hardware: Unspecified → x86
I don't think we should support that <voice> markup in that example. Maybe we should escape it?
Flags: needinfo?(m_kato)
>I don't think we should support that <voice> markup in that example. Maybe we should escape it?
No. WebSpeech should allow providing SSML which is xml too. If you worry about using SAPI5 instead of SSML, see https://bugzilla.mozilla.org/show_bug.cgi?id=835156
And WebSpeech shouldn't stop working, the programs like balabolka don't stop working after provision of incorrect sapi xml.

Maybe you should sanitize WS to plain text until https://bugzilla.mozilla.org/show_bug.cgi?id=835156 is fixed, there can be some rce in sapi and we don't want users' security be compromised.
(In reply to Eitan Isaacson [:eeejay] from comment #1)
> I don't think we should support that <voice> markup in that example. Maybe
> we should escape it?

Sure.  Speak method of SAPI API use XML format.  So we should escape it.
Flags: needinfo?(m_kato)
Depends on: 1237546, 1239946
KOLANICH, our implementation doesn't support SAPI XML now. so if using Firefox 49, it will speak as text.

Could you test this on Firefox 49?
Flags: needinfo?(kolan_n)
Sorry, but I have migrated from Windows to Linux.
Flags: needinfo?(kolan_n) → needinfo?(m_kato)
Flags: needinfo?(m_kato)
Severity: normal → S3

no activity for the last 7 years, closing

Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.