Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Date: Wed, 30 Jan 2013 14:19:12 +0000 (UTC)
From: "Simon MacDonald (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <JIRA.12629820.1359508294487.215422.1359555552896@arcas>
In-Reply-To: <JIRA.12629820.1359508294487@arcas>
References: <JIRA.12629820.1359508294487@arcas>
Subject: [jira] [Commented] (CB-2308) InAppBrowser error event
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CB-2308?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1356650=
4#comment-13566504 ]=20

Simon MacDonald commented on CB-2308:
-------------------------------------

There is an onReceivedError method of the WebViewClient on Android we can u=
se to report errors.
               =20
> InAppBrowser error event
> ------------------------
>
>                 Key: CB-2308
>                 URL: https://issues.apache.org/jira/browse/CB-2308
>             Project: Apache Cordova
>          Issue Type: Improvement
>            Reporter: S=C3=B6nke Rohde
>            Assignee: Shazron Abdullah
>
> Right now there is no InAppBrowser error event.
> That's useful for several reasons and in my case I need it for OAuth. The=
 redirect URL is non-http so I get this error: webView:didFailLoadWithError=
 - The URL can=E2=80=99t be shown
> If I would have an error event containing the failing URL in the payload =
I could actually parse out the refresh/access token etc. from the OAuth flo=
w.
> Besides the error event is also useful in general to get a hook for when =
a URL is not working.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira