[
https://issues.apache.org/jira/browse/CB-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242037#comment-13242037
]
Patrick Mueller commented on CB-362:
------------------------------------
Ah, thanks for the additional info.
Seems to me that whatever behavior we provide could be 'overridden' by an app,
if provided a behavior override setting. While there's prolly little reason to
actually expose such a thing today, perhaps you could at least arrange the code
with this in mind.
I wonder how many people doing this anyway - I never do anything but
single-page apps for mobile. Never use external links. For chrome-less web
apps (save to "home screen"), it's easy to get screwed. You get into a black
hole where (as you pointed out) you have no way of going out, if you load an
external page (I've seen this happen, but can't remember how I made it happen).
And when you shell out to Mobile Safari, then you'll have to restart your app
to get back to it.
> [ios] target="_blank" links should open in browser (ignoring externalhosts)
> ---------------------------------------------------------------------------
>
> Key: CB-362
> URL: https://issues.apache.org/jira/browse/CB-362
> Project: Apache Callback
> Issue Type: Bug
> Components: iOS
> Affects Versions: 1.5.0
> Reporter: Andrew Lunny
> Assignee: Shazron Abdullah
> Labels: externalhosts, whitelist
> Fix For: 1.7.0
>
>
> A link such as this:
> {noformat}<a href="http://google.com"; target="_blank">Google</a>{noformat}
> should open by default in the device's web browser, without being explicitly
> allowed in the plist (externalhosts).
> This is the current (and, imo, expected) behaviour on Android.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
