Hi Henri, the API isn't available in Nightly yet since the code wasn't fully reviewed neither merged yet. You can follow its progress here  and here . If you want to try it before it's merged, just apply the patch  to an updated gecko-dev branch, switch on the *media.**webspeech.**recognition.**enable *and *media.**webspeech.**recognition.**force_enable *flags, and browse to that page again.
Regarding the UI, yes, the experience will be exactly the same in our case: the user will get a prompt asking for permission to open the microphone (I've attached a screenshot below ), but in our case the audio will be sent to the endpoint set in the *media.webspeech.service.endpoint *pref, which the user will be allowed to change (differently than Chrome). But if that's unset, it will send it to Mozilla's own server which is defaulted to in the code.  https://bugzilla.mozilla.org/show_bug.cgi?id=1248897#c18  https://phabricator.services.mozilla.com/D26047  https://www.dropbox.com/s/fkyymiyryjjbix5/Screenshot%202019-10-14%2016.13.49.png?dl=0 On Mon, Oct 14, 2019 at 1:39 AM Henri Sivonen <hsivo...@mozilla.com> wrote: > On Sat, Oct 12, 2019 at 12:29 PM Andre Natal <ana...@mozilla.com> wrote: > > We tried to capture everything here , so please if you don't see your > > question addressed in this document, just give us a shout either here in > > the thread or directly. > ... > >  > > > https://docs.google.com/document/d/1BE90kgbwE37fWoQ8vqnsQ3YMiJCKJSvqQwa463yCN1Y/edit?ts=5da0f63f# > > Thanks. It doesn't address the question of what the UI in Firefox is > like. Following the links for experimenting with the UI on one's own > leads to https://mdn.github.io/web-speech-api/speech-color-changer/ , > which doesn't work in Nightly even with prefs flipped. > > (Trying that example in Chrome shows that Chrome presents the > permission prompt as a matter of sharing the microphone with > mdn.github.io as if this was WebRTC, which suggests that mdn.github.io > decides where the audio goes. Chrome does not surface that, if I > understand correctly how this API works in Chrome, the audio is > instead sent to a destination of Chrome's choosing and not to a > destination of mdn.github.io's choosing. The example didn't work for > me in Safari.) > > -- > Henri Sivonen > hsivo...@mozilla.com > -- -- Thanks, Andre _______________________________________________ dev-platform mailing list email@example.com https://lists.mozilla.org/listinfo/dev-platform