- From: Diogo Resende <dresende@thinkdigital.pt>
- Date: Wed, 2 Dec 2009 18:23:23 +0000
I missunderstood too. It would be great to have the ability to access the microphone and record+upload or stream sound to the web server. -- D. On Wed, 2009-12-02 at 10:04 -0800, Jonas Sicking wrote: > On Wed, Dec 2, 2009 at 9:17 AM, Bjorn Bringert <bringert at google.com> wrote: > > I think that it would be best to extend the browser with a JavaScript > > speech API intended for use by web apps. That is, only web apps that > > use the speech API would have speech support. But it should be > > possible to use such an API to write browser extensions (using > > Greasemonkey, Chrome extensions etc) that allow speech control of the > > browser and speech synthesis of web page contents. Doing it the other > > way around seems like it would reduce the flexibility for web app > > developers. > > Hmm.. I guess I misunderstood your original proposal. > > Do you want the browser to expose an API that converts speech to text? > Or do you want the browser to expose access to the microphone so that > you can do speech to text convertion in javascript? > > If the former, could you describe your use cases in more detail? > > / Jonas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091202/b9ef823f/attachment.pgp>
Received on Wednesday, 2 December 2009 10:23:23 UTC