If that's the case, then I think I lean towards "b) modify cordova-ios 6
to allow both file and custom scheme and then sunset
cordova-plugin-wkwebview-engine?"
The default could be using custom schemes, but if someone wants to
continue using file schemes for whatever reason, a preference could
The data lost is not the topic and I don’t think it’s our duty to avoid it
(but we have to document it and mention it on the release notes). For users
concerned about that, there are plugins available (will probably need some
changes because they were created for the ionic plugin).
There are a few
The only real advantage of using the file protocol is to maintain
backwards compatibility I think. Other than that, it contains a lot of
disadvantages, as the webview disables/restricts a lot of browser
features while on the file protocol, including using XHR to fetch local
resources, which mak
Speaking as someone who raised concerns about this, I don't think
anyone *prefers* file URLs over app schemes, especially given the CORS
issues. However, moving from file URLs to app scheme will result in
apps losing all of their local data (indexedDB, localStorage, cookies,
cache, etc.) due to it
Hi,
What exactly are the advantages to serving with the file protocol if Cordova
doesn't need to?
FWIW, I was never able to get WKWebView working without the additional XHR
plugin, so serving from file holds no obvious advantage for me, at least.
--
Michael Gatto
___
Michael Gatto · Senior So
we should discuss about what's going to happen
with cordova-plugin-wkwebview-engine
cordova-ios 6 is coming soon and it uses WKWebView, but it uses a custom
scheme to serve the app content instead of serving from file protocol.
some people prefers file over the custom scheme,
but cordova-plugin-wk
