W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2010

[whatwg] Speech input element

From: Bjorn Bringert <bringert@google.com>
Date: Tue, 18 May 2010 10:30:01 +0100
Message-ID: <AANLkTil8qrmfnyYIT6nB9CGPb_jmRc09OVM8TaoMnzD9@mail.gmail.com>
On Tue, May 18, 2010 at 10:27 AM, Satish Sampath <satish at google.com> wrote:
>> Well, the problem with alert is that the assumption (which may or may not
>> always hold) is that when alert() is opened, web page shouldn't run
>> any scripts. So should <input type="speech"> fire some events when the
>> recognition is canceled (if alert cancels recognition), and if yes,
>> when? Or if recognition is not canceled, and something is recognized
>> (so "input" event should be dispatched), when should the event actually
>> fire? The problem is pretty much the same with synchronous XMLHttpRequest.
>
> In my opinion, once the speech input element has started recording any event
> which takes the user's focus away from actually speaking should ideally stop
> the speech recognition. This would include switching to a new window, a new
> tab or modal/alert dialogs, submitting a form or navigating to a new page in
> the same tab/window.

Yes, I agree with that. The tricky issue, as Olli points out, is
whether and when the 'error' event should fire when recognition is
aborted because the user moves away or gets an alert. What does
XMLHttpRequest do?

-- 
Bjorn Bringert
Google UK Limited, Registered Office: Belgrave House, 76 Buckingham
Palace Road, London, SW1W 9TQ
Registered in England Number: 3977902
Received on Tuesday, 18 May 2010 02:30:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:23 UTC