[ 
https://issues.apache.org/jira/browse/CB-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Grebnov updated CB-9760:
-------------------------------
    Description: 
There are complains that InAppBrowser and dependent plugins don't work when 
emulated using Ripple. So plugin developers have to use special tricks to 
fallback to default windows.open behavior in case of Ripple, for example

https://github.com/Azure/azure-mobile-services-cordova/blob/master/www/MobileServices.Web.Ext.js#L22

I propose to include this to InAppBrowser plugin so that it work automatically 

  was:
There are complains that InAppBrowser and dependent plugins don't work when 
emulated using Ripple. So plugin developers have to use special tricks to 
fallback on default windows.open behavior in case of Ripple, for example

https://github.com/Azure/azure-mobile-services-cordova/blob/master/www/MobileServices.Web.Ext.js#L22

I propose to include this to InAppBrowser plugin so that it work automatically 


> InAppBrowser: fallback to default windows.open behaviour on Ripple
> ------------------------------------------------------------------
>
>                 Key: CB-9760
>                 URL: https://issues.apache.org/jira/browse/CB-9760
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Plugin InAppBrowser
>            Reporter: Sergey Grebnov
>            Assignee: Sergey Grebnov
>
> There are complains that InAppBrowser and dependent plugins don't work when 
> emulated using Ripple. So plugin developers have to use special tricks to 
> fallback to default windows.open behavior in case of Ripple, for example
> https://github.com/Azure/azure-mobile-services-cordova/blob/master/www/MobileServices.Web.Ext.js#L22
> I propose to include this to InAppBrowser plugin so that it work 
> automatically 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to