Custom webview for iOS devices
xereda last edited by
Just as it is for Android, is there still a need to install a plugin to implement a custom webview for iOS devices?
Is there an officially iOS version of the crosswalk for Cordova?
How to deal with this now !?
Thank you for your help,
There isn’t. One of the reasons being Apple does not allow any other webview to be used other than its own.
actually, you can use this: https://github.com/ionic-team/cordova-plugin-ionic-webview
It is FAR superior to the built in one. But if you do, you MUST include
@ssuess the cordova.js script tag is automatically injected by Quasar. Why do you say you need to add that to index.html?
ssuess last edited by ssuess
@rstoenescu I assure you 100% it is NOT. When using the ionic webview (which replaces the default one), you absolutely need to add the tag. I have done a ton of testing in this area, starting with your default template. If I stuck with the default webview, you are correct it works. But when switching to the (much better and faster) ionic plugin for the webview, other plugins will fail unless this tag is inserted into the html. Try it, you will see.
@ssuess Ah, ok, we’re talking about a custom webview, not the default one, in which case I need to add support for that too. The cordova environment detection needs to be enhanced to detect that webview too.
@rstoenescu if you could, that would be fantastic. I can’t tell you how much better the performance is with the ionic webview, it is night and day.
@rstoenescu did this make it into 0.15 by any chance? I can’t find mention of it in the docs…
MagoSchmidt last edited by
@ssuess Are you experimenting the “two tap problem” inside dialog and modals (buttons and other componentes need two taps to responde?)
I have tried the webview you talked about: https://github.com/ionic-team/cordova-plugin-ionic-webview
It is really fantastic, but the two tap problem remains…
Please take a look at this: https://github.com/quasarframework/quasar/issues/1711#issuecomment-372118483
@MagoSchmidt I have yet to migrate my codebase to 0.15.x, so I could not say, but I have not noticed this problem in my earlier code (based on 0.14.x)
Two tap problem fixed in 0.15.9 - to be released in a few days.