Re: Offline webapps and speech UI

I think we agree that the intention is that typical browsers would by
default follow the web app's requests. There may be settings, modes or
specialized browsers that turn it off by default. As long as the
browser lets the web app know, we won't be any worse off than if the
browser had simply turned off or never implemented the speech input
feature.

/Bjorn

On Wed, Nov 3, 2010 at 3:54 PM, Andy Mauro <Andy.Mauro@nuance.com> wrote:
> It really boils down to what the default setting is ;) If it's to reject
> developer requests for particular reco resources then we're likely not in
> agreement since IMO this will cause apps to not work if a developer uses
> recognizer specific functionality (which as much as I don't like this, is
> the way it is today). If the default is to accept developer requests, and a
> user has to manually modify the setting to use only local resources or an
> alternate network resource, then I think all our goals are met (security,
> privacy, app consistency)
>
> -Andy
>
>> From: Satish Sampath <satish@google.com>
>> Date: Wed, 3 Nov 2010 15:49:51 +0100
>> To: Andy Mauro <Andy.Mauro@nuance.com>
>> Cc: Bjorn Bringert <bringert@google.com>, <Olli@pettay.fi>,
>> <public-xg-htmlspeech@w3.org>
>> Subject: Re: Offline webapps and speech UI
>>
>>> I'm more concerned with the loophole that arises that seems to mean that
>>> browsers can simply use their preferred recognizer all the time irrespective
>>> of developer choice.
>>
>> I don't see that as a loophole, but akin to (2) in your list where the
>> 'paranoid privacy setting' is 'downloading and using a browser which
>> uses my preferred recognizer'.
>>
>> - Satish
>
>
>



-- 
Bjorn Bringert
Google UK Limited, Registered Office: Belgrave House, 76 Buckingham
Palace Road, London, SW1W 9TQ
Registered in England Number: 3977902

Received on Wednesday, 3 November 2010 15:06:17 UTC