incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Updated] (CB-853) Deprecate window.invokeString - use window.handleOpenURL(url) instead
Date Mon, 16 Jul 2012 20:54:34 GMT


Shazron Abdullah updated CB-853:

    Summary: Deprecate window.invokeString - use window.handleOpenURL(url) instead  (was:
Change custom URL scheme handling in iOS)
> Deprecate window.invokeString - use window.handleOpenURL(url) instead
> ---------------------------------------------------------------------
>                 Key: CB-853
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>             Fix For: 2.0.0
> Don't know about the other platforms, but there are two ways it is handled in iOS right
now, we need to consolidate.
> Summary:
> The url scheme passed to the app is a form of inter-process communication, kinda like
how we do gap:// urls, but this is up to the app developer on how they marshal/unmarshal the
url into something they can use.
> Right now in iOS, it is a bit confusing - there are two ways that the URL is handled
and passed off to the UIWebView.
>  1. On *first* app startup, the URL sent is passed off to the UIWebView by setting a
global variable - *window.invokeString*. The URL is passed off untouched (see:
>  2. On *all* launches, the handleOpenURL function is called, and this in turn calls the
global JavaScript function in the UIWebView *window.handleOpenURL()* and this is passed the
URL, untouched (see:
> Apple Doc reference:
> Recommend sticking to handleOpenURL only, deprecate window.invokeString

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message