Forum Replies Created
-
Posts
-
Hi Elliott,
It’s 100% a bug. I installed a totally new wordpress, downloading it from wordpress.org, created a new subdomain, with a new database, downloaded new enfold theme. I just created a single page with a Fullscreen slider and transparent header, added some text around contact form and that’s it (the page is in private content). I made no additional changes to wordpress and enfold theme.
I opened the page on an android 5.0.2 mobile phone in incognito mode in chrome and firefox, clicked once on the page in non important part of it (ig. plain text) and than clicked on input form and the same thing happened, keyboard appeared on screen and site scrolled down so you I couldn’t see input form that I wanted to write in. I saw that if you don’t click on the site prior to clicking input form, everything works fine.It’s impossible that you can’t reproduce the problem on your test setup, You are probably doing something wrong.
Regards,
TomaszHi Elliott,
For me the biggest problem is how it behaves on mobile devices (i checked it only on android). Normally input form doesn’t behave like this on android. To prove it I created a second page without Fullscreen slider and everything works there fine, you can find it in private content. It is a bug in enfold theme.
As it is for your suggestion that “I can always to scroll back up after software keyborad displays” the only people that use input form are the clients, and I don’t see how to tell each of them something like that.
Cheers,
Hi Elliot,
I did what you said, deleted enfold theme via FTP, uploaded new one and deactivated all plugins. I still have the same problem on mobile devices, that is:
“when you click input form, keyboard appears on screen and site scrolls down so you cant see input form that you are writing in”.The problem happens only with Fullscreen Slider on the page. If I remove Fullscreen Slider, the input form starts to behave normal.
I’ve duplicated the whole site to a test domain, on a different server (the problem still appears), on which you can test the bug as you want. The credentials are in Private Content.
Cheers,
