- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Sat, 11 Dec 2010 14:55:26 +1100
- To: Toby Inkster <tai@g5n.co.uk>
- Cc: Robin Berjon <robin@berjon.com>, David Singer <singer@apple.com>, HTML WG <public-html@w3.org>, Frederick Hirsch <Frederick.Hirsch@nokia.com>, Dominique Hazael-Massieux <dom@w3.org>, Thomas Roessler <tlr@w3.org>
On Thu, Dec 9, 2010 at 3:19 AM, Toby Inkster <tai@g5n.co.uk> wrote: > On Wed, 8 Dec 2010 17:07:46 +0100 > Robin Berjon <robin@berjon.com> wrote: > >> The argument that there is a potential clash is certainly acceptable. >> I wonder if one potential work around is to only accept the capture >> parameter on {audio,video,image}/*. (Just a thought.) > > I think you could meaningfully capture text/plain from a microphone > using speech recognition software. How does this relate to the new <device> element and in particular with the Stream API, see http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#devices ? I am a bit confused - isn't the Stream API meant to be used for capturing / recording audio/video? Silvia.
Received on Saturday, 11 December 2010 03:56:19 UTC