Eingeschränkter Support in der Zeit vom 22.Dez bis 05. Jan 2014
In der Zeit vom 21.12.15 bis 03.01.16 arbeitet unser Büro in Münster mit einer Minimalbesetzung. Bitte haben Sie Verständnis dafür, wenn Bestellungen und die Beantwortung von Supportanfragen in dieser Zeit länger dauern, als Sie es von uns gewohnt sind. In vielen Fällen hilft auch unser Support-Center weiter....
Wir wünschen Ihnen und Ihren Familien ein frohes Weihnachtsfest, sowie einen guten Rutsch ins neue Jahr.

 

Bug Report: Speech Recognition not available on Chromium

Reproduktion

1. Open Windows Site Kiosk Chromium browser.

2. Visit one of the following:
https://hbreavis.moybo.com/.
https://davidwalsh.name/demo/speech-recognition.php

3. Speech recongition API is not available. (Compare with the same site in native Chrome browser.)

Beschreibung

We are using a Windows Site Kiosk with the Chromium browser.
We need to open a webpage using the Speech Recongition API: https://hbreavis.moybo.com/.

The page works fine in Chrome browser on the same machine, however in Site Kiosk, the Speech Recongition API is not available.
When tested on multiple sites, the microphone access works fine, the only issue seems to be the recognition API which does not work on any webpage we tried.

Can you advise us how to turn the support on?

Antwort: (1)

Re: Speech Recognition not available on Chromium 24.01.2020 09:18
Hello,

This is not a bug but is caused by the fact that the corresponding API keys are not integrated into the Chromium CEF engine used by SiteKiosk.
If you want to test it outside of SiteKiosk:
SiteKiosk 9.7.5232 uses Chromium 76.0.3809.132 Windows 32 Bit. Here you can find the corresponding Chromium test application for download (unzip 2x and run the cefclient.exe in the "Release" folder) which is currently used in SiteKiosk 9.7.5232 (Chromium 76.0.3809.132 Windows 32 Bit):
http://opensource.spotify.com/cefbuilds/cef_binary_76.1.13%2Bgf19c584%2Bchromium-76.0.3809.132_windows32_client.tar.bz2

Solution you can try:
If this speech recognition API is required, you can test if it works by adding the appropriate API key yourself.
See: “Providing Keys at Runtime” at this page https://www.chromium.org/developers/how-tos/api-keys
This page explains it a little easier.:
https://gist.github.com/cvan/44a6d60457b20133191bd7b104f9dcc4

Regards,
Michael Olbrich