Open Bug 1425523 Opened 2 years ago Updated 10 months ago

Implement SSML parsing at SpeechSynthesisUtterance


(Core :: Web Speech, task)

57 Branch
Not set





(Reporter: guest271314, Unassigned)


User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/62.0.3202.94 Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce:

Pass valid SSML as first argument SpeechSynthesisUtterance

Actual results:

SSML is not parsed

Expected results:

SSML to be parsed
Component: Untriaged → Web Speech
Product: Firefox → Core

#2 Chromium is now performing some SSML tests though as far as am able to gather - at extension code - not related to Web Speech API, at least from what can gather by the names of the files and lack of explicitly stating the tests and the language in the comment

This change doesn't integrate the ssml parser; this will be done in a follow-up change to this one.;; #61 was deleted due to again referencing that SSML parsing is possible given the effort to do so (a start using JavaScript

From a front-end perspective, SSML parsing should not be abstracted to code that is not reachable/modifiable by the developer/user without undue restrictions as to how the markup is parsed to audio output. One example of the varying interpretations of the SSML specification, and implementation are




elements, where when tests are run on SSML third-party web services, there are different implementations. If recollect correctly, *oogle "Home' service, *mazon "*lexa", *BM *luemix inserted pause or did not insert pause arbitrarily as the language of the specification does not precisely specify what should NOT occur (

Type: defect → task
You need to log in before you can comment on or make changes to this bug.