Doesn't work with plugins - whitelist and inAppBrowser

[eddieSullivan]

Both of these plugins fail to work in Ripple.
The whitelist plugin gives the following error message every ten seconds:

No Content-Security-Policy meta tag found. Please add one when using the cordova-plugin-whitelist plugin.

The InAppBrowser does not fire the loadstart event.

[TimBarham]

Regarding the No Content-Security-Policy meta tag found message: Can you explain why you regard this as "failing to work? That message is output (to the console) by the plugin if your content doesn't have a Content-Security-Policy meta tag (and isn't displayed if your content does have the tag). That console message surfacing in Ripple seems to me to be expected behavior.

[eddieSullivan]

Sorry, I should have been clear. The meta tag is indeed present in the source HTML file, and the warning does not appear when run on the Android emulator platform.

[TimBarham]

Hmmm, that's weird. I can't repro (that is, I see the message if I don't have the CSP meta tag, and don't see it if I do). The plugin's logic that handles this is very basic, and it doesn't seem it is doing anything where Ripple have any impact.

Couple of questions:

• What version of Ripple are you using (ripple version from a shell prompt will tell you that)?
• Are you able to repro with a blank Cordova project (as in "cordova create foo")?

[TimBarham]

Oh, and the InAppBrowser problem is because the plugin specifically bypasses Ripple here:

    // special patch to correctly work on Ripple emulator (CB-9760)
    if (window.parent && !!window.parent.ripple) { // https://gist.github.com/triceam/4658021
        module.exports = window.open.bind(window); // fallback to default window.open behaviour
        return;
    }

[eddieSullivan]

I wonder why InAppBrowser has that "special patch"? I will try removing that check and see if it helps. If not, I'm sure I can find a workaround.

The Content-Security-Policy meta tag issue appears to have been user error. Apparently there's something wrong with my build setup, because clearing out the www directory and rebuilding caused the issue to go away. I'll keep an eye on the issue and update you if I can reproduce it more reliably.
Thanks for your help!

[TimBarham]

Ok, thanks @eddieSullivan. Good news about the CSP.

I believe that code was added to InAppBrowser because some apps relied on a real window being opened (often hidden) to do stuff (where-as Ripple would just display a popup showing the URL that would have been opened, but didn't actually open it). The proper fix, I think, will be to modify Ripple in some fashion to actually open a window (then remove that code from InAppBrowser).

[eddieSullivan]

Ah, I see. That seems about right, because when I remove that special patch, I see a faked-out page (although not in a popup) with a "InAppBrowser Emulation It is like a browser, only it is all up in your app" message.

Ok, thanks again. If I have some time I'll dig more into the proper fix you describe.