Blog post up:
https://cordova.apache.org/news/2018/08/01/future-cordova-ios-webview.html
Retweet this:
https://twitter.com/apachecordova/status/1027397670430601216
On Thu, Aug 9, 2018 at 9:55 AM Shazron wrote:
>
> Julio,
> Darryl mentioned " iframes being cross origin (so no accessing the
> paren
Julio,
Darryl mentioned " iframes being cross origin (so no accessing the
parent/child document)" which means that it is a break from existing
UIWebView behaviour that users expect, that will now break. There are
workarounds:
https://medium.com/@DrawandCode/how-to-communicate-with-iframes-inside-w
What's exactly the iframe problem?
El mié., 8 ago. 2018 a las 10:05, Niklas Merz ()
escribió:
> +1
>
> I am really happy to hear about the WKwebview future. I tried WKwebview
> some time ago and it did not work well with our app. I think the changes
> mentioned in the blog post will make the tran
+1
I am really happy to hear about the WKwebview future. I tried WKwebview some
time ago and it did not work well with our app. I think the changes mentioned
in the blog post will make the transition to WKwebview easier. Not supporting
some features like iframes may be an issue for some users t
+1. Please post it.
I think it is better to put it out there and get feedback from the wider
community, than sit and try to perfect a message here with a subset of
subscribers.
We can only do the best we can with what we have.
Regarding things like iframes, I am not sure they are worth keeping ar
If there are no further comments regarding the blog post, I will
publish it by EOD (Pacific Time) Wed August 8th, 2018
https://github.com/apache/cordova-docs/pull/867
On Wed, Aug 8, 2018 at 3:14 PM Shazron wrote:
>
> Apple has other goals with WKWebView (a lot deals with making it more
> secure),
Apple has other goals with WKWebView (a lot deals with making it more
secure), and I doubt they are aligned with Cordova's goals (although
they did a patch to load file urls for iOS 9 I believe, that helped us
avoid the local webserver route). I think almost all of us know that
WKWebView usage by C
We definitely have to explore this more. I doubt we can ever be
perfect at the first run at it, but we've got to lay the foundation
for the eventual patches.
On Fri, Aug 3, 2018 at 11:30 AM Darryl Pogue wrote:
>
> One concern with the Oracle plugin is that it's only patching the
> obvious cases
My impression as a user on this is that, since the very first few
prototypes with WKWebView from Shazron and some others, to later the Ionic
attempts at solving/masking the usual issues, to the current situation
where we have a deprecated UIWebView, is still the same as it was at the
start: using W
One concern with the Oracle plugin is that it's only patching the
obvious cases of XHR and fetch, but doesn't handle things like iframes
being cross origin (so no accessing the parent/child document) or
local image assets being cross origin when drawn to canvas (thus
tainting the canvas and making
Our policy has been we support the currently shipping iOS version,
plus one back. This is because of device version testing complexities.
It may work on older iOS versions if we code it with the right
safeguards, but that is not guaranteed. When iOS 12 ships this fall,
we would drop iOS 10 support
On Sun, Jul 15, 2018 at 11:39 PM Shazron wrote:
>
> 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
This ha
Is there a place where the most popular alternative webview engines
are documented?
Should we add this?
Should I raise an issue on cordova-docs?
On Thu, Aug 2, 2018 at 11:38 AM Jan Piotrowski wrote:
>
> That would be really great. Thanks!
>
> 2018-08-02 17:16 GMT+02:00 Shazron :
> > We could --
That would be really great. Thanks!
2018-08-02 17:16 GMT+02:00 Shazron :
> We could -- I can just add a suffix or prefix...
> On Thu, Aug 2, 2018 at 11:14 PM Jan Piotrowski wrote:
>>
>> Couldn't the class names be changed when integrating the plugin?
>> Because the console stuff is still messing
We could -- I can just add a suffix or prefix...
On Thu, Aug 2, 2018 at 11:14 PM Jan Piotrowski 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 :
> > yup, the class name c
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 :
> yup, the class name conflict is unavoidable -- it's like when we
> integrated the console plugin.
>
> The bridge plugin will be able to
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 Ion
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 :
> Many Co
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 :
> Please review the draft of the blog pos
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 wrote:
>
> I've done with my review with all the issues that need to resolved
> with the plugin before it c
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'
21 matches
Mail list logo
