-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WKWebView iOS Header UI Glitch #49
Comments
Hi Harty, give this a try:
Hope this helps |
so does it work? your welcome buddy ... welcome. |
Yeah it works, I'm sorry for just closing the issue without saying a thing. |
Glad it worked :) |
Hi @FredeHo , @hartherbert do you had the same problem ? Many thanks for your help. |
This is not working for me. The header still goes upwards on iPhone X. The recommended keyboard plugin by the ionic team is now: https://github.com/ionic-team/cordova-plugin-ionic-keyboard which does not have this.keyboard.disableScroll(true);. I tried using '' from the new plugin. This does not work as well... @EddyVerbruggen Since this is a paid plugin, shouldn't we get some sort of support? Thanks. |
@jeffreyramia This worked for me if it helps: #73 (comment) |
@hobbydevs which plugin you have used? |
Hey @EddyVerbruggen I wanted to say thanks to the awesome plugin you wrote!
It works great with WKWebView on my app. The only thing I noticed since I started to use WKWebView is that when I open the native-keyboard and close it (by clicking the view) the header is pulled up by the space the inputfield down under needs. To demonstrate you that I added two buttons in the View
Arrow-Down-Button to hide the native-keyboard only using
Arrow-Up-Button to show the keyboard again using
In action, it looks like this:
In the video you see that when I open up the keyboard to type something and it than closes, the header is cutted. And when I hide the keyboard, the header is totally normal again. this is only happening since I installed the Cordova-Plugin-WKWebView-Engine from the Ionic-Team
I don't really know what is going wrong here but for me it seems like the native input-field is pushing up the whole "screen" or Webview.
Any suggestions?
The text was updated successfully, but these errors were encountered: