Re: Web Intents: Proposed modifications to the spec regarding registration

What is the use case for calling isIntentHandlerRegistered?


On Wed, Aug 29, 2012 at 6:59 AM, Josh Soref <jsoref@rim.com> wrote:
> James wrote:
>> Can you elucidate what you mean by applying same-origin policy to
>> isIntentHandlerRegistered()?
>
> What it means that a site "example.com" can call:
>     DOMString isIntentHandlerRegistered(DOMString action, DOMString? mimeType, DOMString url);
>
> isIntentHandlerRegistered(action, mimetype, "http://example.com/someintent")
>
> but it can't call:
> isIntentHandlerRegistered(action, mimetype, "http://example.net/someintent")
> (well, it can, but it should not get a truthful answer.)
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Tuesday, 4 September 2012 17:06:56 UTC