This could be an issue that is very specific to a device I suppose (in this case my samsung galaxy tab 10.1) but its somewhat irritating. When I have an HTML app and select a text box for input, the screen flickers black while trying to scroll and even occasionally while I'm typing. The only thing that is not black during this time is the text box.
Anyone else have this issue before?
This is a persisting problem that's really causing some headache... I don't suppose anyone out there can test this issue on their device?
Hi Paul,
Can you, please, attach/send me a project?
Sure, where should I send it?
Also, its not anything in particular that causes it in my project. I've made a new project with nothing but a field and a bunch of line breaks and it still causes the same thing to happen on my samsung galaxy tab 10.1.
You can either attach the archive here or at ovidiu at mosync dot com.
Just thought I'd check in and see if you got the email?
I'm still not sure how to proceed... don't mean to be overly persistent but hoping for some input.
I've at least made some progress in identifying the issue. I've found a stackoverflow thread that talks about this happening in PhoneGap, I assume the theory is the same with MoSync and have verified it to be present in both. Any thoughts or suggestions?
Interesting. This code seems to fix the problem
The solution is to enable hardware-acceleration in the android manifest.
I'll speak to the team and see if we can get this option into a nightly build ASAP.
I've seen it work with the hardware acceleration code, but it also changed how fonts were rendered for me and I've read it drops performance significantly on some devices. Not sure there are any other options though.
Just wanted to confirm this fix and say thanks. What I assume was my same fix with PhoneGap resulted in some horribly weird anti-aliasing issues with text. This is clearly better but the app seems a bit sluggish. Too early to tell if its related though.
Again, thanks for the help guys. Keep up the great work.
Ugh, sorry to bump this thread but it turns out the issue is still there though by pure coincidence I found a workaround (though not perfect, it works for my solution). Having a div with contenteditable="true" allows you to accept input without the issue being present. You can then store the content in a hidden input via keypress events. Hope this helps someone else with the same issue.