We could -- I can just add a suffix or prefix... On Thu, Aug 2, 2018 at 11:14 PM Jan Piotrowski <piotrow...@gmail.com> wrote: > > Couldn't the class names be changed when integrating the plugin? > Because the console stuff is still messing with people :/ > > 2018-08-02 17:01 GMT+02:00 Shazron <shaz...@gmail.com>: > > yup, the class name conflict is unavoidable -- it's like when we > > integrated the console plugin. > > > > The bridge plugin will be able to load any webview engine plugin that > > has already been installed, not just the main 2. I didn't want to > > confuse people with too much information, since this is not an Ionic > > blog post. > > On Thu, Aug 2, 2018 at 10:50 PM julio cesar sanchez > > <jcesarmob...@gmail.com> wrote: > >> > >> As long as we don't break pluggable webviews, I don't think it's needed, > >> there are other wkwebview plugins (from telerik, oracle, etc). > >> > >> But as some (or all) of them started as forks, there will be probably > >> problems with duplicate class names. > >> > >> 2018-08-02 16:42 GMT+02:00 Jan Piotrowski <piotrow...@gmail.com>: > >> > >> > Many Cordova users out there are probably using > >> > https://github.com/ionic-team/cordova-plugin-ionic-webview. Does this > >> > play any role in regards to the blog post? Should this maybe be > >> > mentioned as an anticipated question? > >> > > >> > 2018-08-02 16:31 GMT+02:00 Shazron <shaz...@gmail.com>: > >> > > Please review the draft of the blog post about this: > >> > > "The Future of the iOS WebView in Apache Cordova" > >> > > https://github.com/apache/cordova-docs/pull/867 > >> > > On Mon, Jul 16, 2018 at 2:38 PM Shazron <shaz...@gmail.com> wrote: > >> > >> > >> > >> I've done with my review with all the issues that need to resolved > >> > >> with the plugin before it can be baked in to the platform for a major > >> > >> version release. I'm going to discuss issues with respect to migration > >> > >> of developers from UIWebView (features that will be lost or are > >> > >> different) > >> > >> > >> > >> 1. Cookies don't persist. This is a WebKit bug, but someone has > >> > >> created a plugin for a workaround. See > >> > >> https://issues.apache.org/jira/browse/CB-12074 > >> > >> 2. Can't delete cookies. This is/was a WebKit bug (2015), need to test > >> > >> for the iOS 11/12. See https://issues.apache.org/jira/browse/CB-11297 > >> > >> 3. Can't execute JavaScript code in the background. There are several > >> > >> issues related to this. See > >> > >> https://issues.apache.org/jira/browse/CB-12815 > >> > >> 4. XmlHttpRequests don't work, because of Cross-Origin Resource > >> > >> Sharing issue (CORS). There is a workaround plugin created by Oracle > >> > >> (UPL licensed, which is Apache-2.0 compatible). See > >> > >> https://issues.apache.org/jira/browse/CB-10143 > >> > >> 5. Migration of localStorage from UIWebView. There is a migration > >> > >> plugin available. See https://issues.apache.org/jira/browse/CB-11974 > >> > >> > >> > >> Of course there are several bugs also that need to be resolved. List > >> > >> here: https://s.apache.org/QfsF > >> > >> > >> > >> Out of the 5 issues, 3 (external) plugins are available for the > >> > >> issues, 2 require minor code changes. > >> > >> > >> > >> For a solution to issue 5, I am proposing a proxy webview engine > >> > >> plugin that will: > >> > >> 1. Read a preference to use a particular webview engine > >> > >> 2. Proxy the selected webview engine's interface from its interface > >> > >> > >> > >> This proxy will possibly help with migration and testing, so users can > >> > >> "beta test" WKWebView now for existing apps (and switch back if there > >> > >> are problems). This is like a "feature flag" that I mentioned before, > >> > >> but at runtime, for users. > >> > >> > >> > >> This proxy webview engine plugin can also possibly help with > >> > >> InAppBrowser, I'm not sure (since that plugin has more hooks into a > >> > >> webview's interface). > >> > > > >> > > --------------------------------------------------------------------- > >> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> > > For additional commands, e-mail: dev-h...@cordova.apache.org > >> > > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> > For additional commands, e-mail: dev-h...@cordova.apache.org > >> > > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org