[Webkit-unassigned] [Bug 60170] [Chromium] Speech-enabled input fields need the ability to trigger without a click

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=60170





--- Comment #20 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2011-08-25 15:48:22 PST ---
(In reply to comment #13)
> (We could provide startSpeechInput and stopSpeechInput also, if we
> think they'd be needed or useful. However, a startOrStopSpeechInput is
> still needed because when the user triggers speech input by an action
> in the browser process, whether by a key, context menu, etc. it
> doesn't make sense to send one round-trip to the renderer process to
> determine the current state, then flip the state in another RPC, with
> a possible race condition. Having a startOrStopSpeechInput method
> exactly mimics the user behavior when they click on the microphone
> icon, which is what we want.

OK, I see that you addressed my question here.

I don't think these IPC considerations have much to do with how the WebKit API is shaped.  You could very easily have an IPC named StartOrStopSpeechInput, which could use local WebKit APIs to determine whether it makes sense to call startSpeechInput or stopSpeechInput.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.