No description provided.
Comment on attachment 8979685 [details] [diff] [review] Enable WebSpeech synthesis in Android. r?smaug rs+ I guess. How much testing has it got? Does it work with geckoview?
Attachment #8979685 - Flags: review?(bugs) → review+
(In reply to Olli Pettay [:smaug] from comment #2) > Comment on attachment 8979685 [details] [diff] [review] > Enable WebSpeech synthesis in Android. r?smaug > > rs+ I guess. > How much testing has it got? Does it work with geckoview? Not much testing, that's why I think it should be enabled. Would you do this differently? Only enable in pre-release? I figured if it rides the trains we should uncover any issues there may be. It works in geckoview.
Would it be helpful to have the web compat team do some testing in Nightly? Are there particular sites we are concerned about?
(In reply to Panos Astithas [:past] (please ni?) from comment #4) > Would it be helpful to have the web compat team do some testing in Nightly? > Are there particular sites we are concerned about? Thanks! This kind of testing would be amazing. I don't actually know of popular sites that use this :) I made a demo site a while back: http://eeejay.github.io/webspeechdemos/ Note, to compare apples to apples, you need to run this against android chrome. the android platform tts is not great, so we couldn't implement every feature, like pause. chrome had to leave things unimplemented as well.
Oops. Forgot to tweak the interfaces test..
Attachment #8982290 - Flags: review?(bugs)
Attachment #8979685 - Attachment is obsolete: true
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/7fa83e49f708 Enable WebSpeech synthesis in Android. r=smaug
Doc updates got done here: https://bugzilla.mozilla.org/show_bug.cgi?id=1184142#c45 It's on Firefox 62 for developers: https://developer.mozilla.org/en-US/Firefox/Releases/62#APIs
Devices: - Nexus 5 (Android 6.0.1); - Nexus 9 (Android 6.0.1); - Samsung Galaxy Tab 3 (Android 7.0). Verified this using the site provided by Eltan in Comment 5. There was no noticeable difference between Chrome and FF when testing this, speech worked perfectly on all of the devices using a variety of pitch, rate and volume.
You need to log in before you can comment on or make changes to this bug.