Skip to content
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.

config.xml / DisallowOverscroll preference doesn't seem to be working #153

Open
nodefish opened this issue Jun 25, 2017 · 6 comments
Open

Comments

@nodefish
Copy link

nodefish commented Jun 25, 2017

With this plugin the WKWebView seems to ignore the DisallowOverscroll setting in config.xml (<preference name="DisallowOverscroll" value="true" />). It seems to occur immediately after focusing an input, which causes the keyboard to appear and the page to shift upwards. After doing this even just once, the webview becomes permanently overscrollable.

For testing purposes, I switched to the standard WKWebView engine (1.1.3) and the issue did not occur (the webview remained fixed).

This is an awesome plugin and I'd prefer to use this one over the standard one. Thanks!

@Crylion
Copy link

Crylion commented Jul 12, 2017

I have the same problem. My app definitely has a bounce problem now and the disallowOverscroll option was needed to fix that.
Apparently this got removed in 71135cb by @manucorporat but no other way to configure wkWebView.scrollView.bounces was introduced, thus leaving us with no option to combat the overscroll issue? Can someone explain this decision, or whether there is another way I'm not seeing?

@manucorporat
Copy link

@Crylion can you submit a video? are you using a ionic2?

I just don't see the point of that point for Ionic 2, that's why it was removed. I will add it back if I can understand the use case!

@Crylion
Copy link

Crylion commented Jul 12, 2017

Ah okay I was wondering whether the removal of the setting was possible because the problem does not exist for you anymore.
I must admit, that we don't use ionic (except for a few ionic-native wrappers). It's a plain Angular (4.2.6) app without the ionic framework. We just thought that it would propably be better to use this fork of the wkwebview-engine plugin, because it seemed to be better maintained than the original apache version :)
So I guess that by using the UI Components of Ionic 2, the scrolling issues are fixed by those?
Would you say that we are better off using the apache version then?

Thanks for your response

@JulianLaval
Copy link

Seconding @Crylion - not using Ionic, but using this fork as it is more actively maintained and streamlines the integration of a local server. I understand that Ionic is the priority, however, so would be curious to hear your thoughts on whether this is a valid use case, @manucorporat ?

@bytex64
Copy link

bytex64 commented Aug 30, 2017

I just wanted to add another voice to the "I don't use ionic but I use ionic wkwebview because it's better and I'd like to have DisallowOverscroll support."

manucorporat pushed a commit that referenced this issue Sep 20, 2017
* Respect DisallowOverscroll property

Fixes issue #153

* Code from Cordova repo
@manucorporat
Copy link

We added it back! sorry for the inconvenience. But for the ionic users I recommend to leave the default value.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants