W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2011

Re: [DRAFT] Web Intents Task Force Charter

From: Rich Tibbett <richt@opera.com>
Date: Thu, 10 Nov 2011 19:47:09 +0100
Message-ID: <4EBC1C2D.2010906@opera.com>
To: Dave Raggett <dsr@w3.org>
CC: public-device-apis@w3.org
Dave Raggett wrote:
> On 10/11/11 16:20, Clarke Stevens wrote:
>> Dominique,
>>
>> Your example below is very helpful. I have a couple of follow-up
>> questions:
>>
>> * I want a single web page with the UI exposed to the user. The user
>> should not see any additional tabs or browser windows (except perhaps a
>> pop-up child dialog listing available relevant services). Is this
>> possible?
>
> Does that have to be a regular web page, or could it be generated by the
> browser as a trusted UI component?
>
> I am thinking of the way Android pops up a selector UI for choosing
> between the installed applications for handing an intent, e.g. when you
> have multiple NFC apps installed.
>

This may just be a case of conflicting terminology for the same thing.

The 'intent picker' would always be a trusted UI component in a Browser 
environment, displayed whenever an intent is invoked from a web page. 
When the user selects an 'intent handler' from the picker the behavior 
will be to either open a new web page pointing to the 'intent target' 
or, tbd, a non-visible window with identical functionality that is 
maintained behind-the-scenes by the UA (as requested by Clarke above - 
hence only the web page that invoked the initial intent remains displayed).
Received on Thursday, 10 November 2011 18:47:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT