InAppBrowser does not use Crosswalk

4 posts, 0 answers
  1. Giancarlo
    Giancarlo avatar
    9 posts
    Member since:
    Jul 2015

    Posted 30 Oct 2015 Link to this post

    I have selected Cordova 4.0 within AppBuilder and have selected Crosswalk as my Web View. However, in debugging mode, I see different versions of "Chrome". Additionally, if via javascript I output navigator.userAgent to the page, I get two different versions and the InAppBrowser view does not mention Crosswalk like the Cordova webview does. Is there a fix available for this? We'd really like to rely on the Crosswalk webview for the app and InAppBrowser.

    Thanks!

  2. Dimitrina
    Admin
    Dimitrina avatar
    3769 posts

    Posted 04 Nov 2015 Link to this post

    Hello Giancarlo,

    Generally, the core Cordova InAppBrowser plugin works with the Default WebView and not with Crosswalk. You can also refer to the Cordova's Wiki on InAppBrowser

    I am not sure if I understand your request right. You say you use Cordova 4.0 within AppBuilder and have selected Crosswalk as your Web View. Would you please clarify what do you mean that in debugging mode, you see different versions of "Chrome"? How do you verify this?

    As to the second point, it seems there is already a plugin Cordova InAppBrowserXwalk Plugin which combines InAppBrowser and Crosswalk, however, for the moment it is not verified to be working fine in AppBuilder. You can still check it out and share your observations.

    Further, I also suggest going through the benefits and the drawbacks of using Crosswalk in Android applications.

    I hope this helps.

    Regards,
    Dimitrina
    Telerik
     

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

     
  3. Giancarlo
    Giancarlo avatar
    9 posts
    Member since:
    Jul 2015

    Posted 04 Nov 2015 in reply to Dimitrina Link to this post

    Dimitrina,

    Thanks for your reply. Sorry, "in debugging mode" was to say in the console the output of navigator.userAgent. Additionally, this is done on device debugging and not within the simulator. 

    I should have clarified, I'm using the Visual Studio Telerik AppBuilder extension, I have added screen shots in reply to your question.

    I will check out the InAppBrowserXwalk plugin, however, the API seems to be much different than the InAppBrowser (albeit nicer) given the "options" are input as an object and not a comma separated list of options in a string.

    I have seen that pro/con page but thanks for mentioning it. We want the performance improvement. Also, we are ok with the drawbacks as none of them are a concern. We have a fully developed web app for our customers that we are integrating into the app. There are some integration points (like camera use) that are nicer in our app than when you just use the web browser on a mobile device. Additionally, we can control the resolution of the camera which helps with browser crashing for users that have ultra hi-res cameras on their mobile device.

     

  4. Dimitrina
    Admin
    Dimitrina avatar
    3769 posts

    Posted 06 Nov 2015 Link to this post

    Hello,

    Thank you for clarifying my question. I am afraid this would be the expected behavior though. The reason is the core Cordova InAppBrowser plugin works with the Default WebView and not with Crosswalk. 

    Regards,
    Dimitrina
    Telerik
     

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

     
Back to Top