WebView-based Android browsers don't allow webkitSpeechRecognition javascript library calls to function as expected though they work fine in Chrome/Chromium
Reported by
tbarstow...@gmail.com,
Jul 15 2016
|
||||||
Issue descriptionExample URL: http://codepen.io/anon/pen/GqyqVa Steps to reproduce the problem: 1. View http://codepen.io/anon/pen/GqyqVa with a WebView based browser (KioskBrowser, etc) 2. Click the icon 3. No prompt for voice input ever occurs What is the expected behavior? 1. From http://codepen.io/anon/pen/GqyqVa with a Chrome/Chromium browser... 2. Click the icon 3. Voice input prompt occurs 4. Users may say 'search for foobar' or 'find foobar' (with annyang code) or 'foobar' (without annyang library running). 5. Voice input translation occurs (on successful translation) 6. Translated input is submitted on the form. 7. User sees results from voice input in OPAC query. || 5. Voice translation does not occur-- nothing is heard/understood or translated 6. Form continues to be presented until successful form input occurs. What went wrong? For some reason webkitSpeechRecognition seems to be disabled/blocked from firing correctly in WebView in Android 5.1.1. I am not sure if this is intentional or not but found no other tickets mentioning it. I have worked with the devs at KioskBrowser and they did some testing and seemed to think it's not them and it's at the webView level. It's also strange that no error message I have designed to inform the user is able to alert the end user is able to fire... ie. WebView thinks it has webkitSpeechRecognition but seems to not be able to run it. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? Yes Chrome version: 51.0.2704.81 Channel: stable OS Version: 5.1.1;SM-T670 Build/LMY47X Flash Version: -- I hope this is the correct place to put this request in-- if not could someone please direct me to the appropriate tracker.
,
Jul 16 2016
,
Jul 16 2016
,
Jul 18 2016
I can't recall for sure if this is supposed to be working or not but I think it's intentionally disabled for some reason? If so then it should be feature-detectable as not supported..
,
Jul 28 2016
yes webkitSpeechRecognition is currently not available in webview (see e.g. crbug.com/487255) and is not exposed by webview, so in that sense it's 'feature-detectable' as not existing
,
Aug 1 2016
That doesn't match the report here, which says taht webkitSpeechRecognition exists.
,
Aug 1 2016
I am pretty sure it is not exposed in webview (i.e. we specifically test for it). We did that a while back, so it should apply to M51 as well.
,
Aug 1 2016
Oh, right. We were accidentally exposing it but Tim fixed this in issue 483889 , which went into webview 44 and later. It looks like webview 42 and 43 had it exposed but nonfunctional (possibly some earlier versions as well? it's not clear when it was introduced) Reporter, what version of webview are you using? If you have the current version then it won't be there at all and your feature detection correctly reports this for me.
,
Aug 17 2016
tbarstow.dml@: can you confirm which WebView version your KioskBrowser used? It seems this is supposed to be working as intended now (i.e. not exposed).
,
Sep 9 2016
tbarstow.dml@ di you get any chance to look at this yet?
,
Oct 3 2016
Closing in lack of activity/feedback. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tbarstow...@gmail.com
, Jul 15 2016