Open
Bug 1596819
Opened 5 years ago
Updated 2 years ago
Other languages are being voice recognized as English incorrectly when using Google Translate and a certain endpoint is set
Categories
(Core :: Web Speech, defect, P3)
Core
Web Speech
Tracking
()
NEW
People
(Reporter: danibodea, Unassigned)
References
Details
Note
- When adding the "media.webspeech.service.endpoint" pref with the value "https://dev.speaktome.nonprod.cloudops.mozgcp.net/" and going to the Google Translate page, select any other language than English as the input language and attempt to use the voice recognition feature to input words into the input box, it will be noticed that the WebSpeechAPI will attempt to understand English, no matter which language would be spoken.
Affected versions
- Nightly v712.0a1
Affected platforms
- all and Fenix
Steps to reproduce
- Open Nightly v72.0a1 from 2019-11-15
- Open about:config
- Flip to following prefs si "true":
media.webspeech.recognition.enable
media.webspeech.recognition.force_enable - Create a string pref called "media.webspeech.service.endpoint" with the value " https://dev.speaktome.nonprod.cloudops.mozgcp.net/".
- Go to https://translate.google.ro/
- Select any other language than English.
- Click the microphone icon/button and speak the selected language into the microphone.
Expected result
- Words of the selected input language will be understood and input into the box.
Actual result
- English words are being shown as understood.
Additional notes
- This issue is present al all platforms, including Fenix v72.0a1 191115 on Android.
- This issue does not occur on the Chrome browser.
- If the "media.webspeech.service.endpoint" pref with the "https://dev.speaktome.nonprod.cloudops.mozgcp.net/" value is added in about: config, then the issue would not happen.
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:anatal, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(anatal)
Updated•4 years ago
|
Flags: needinfo?(anatal)
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•