10-03-2012 11:54 PM
I have an HTML5 application with a notes Page. Everytime the note is edited and the keyboard comes up, the screen content is bumped up. How can I make sure the content is not bumped up??
10-04-2012 07:26 AM
We do not re-render your content in a webview in the latest WebWorks SDK based on the keyboard, so the keyboard should just be drawn on top. Are you using a Dev Alpha device? Or is this a Playbook issue?
Can you provide a screen shot of the issue?
10-04-2012 08:38 AM - edited 10-04-2012 08:48 AM
This is a PlayBook matter. Attached below is a screenshot. Note the bottom toolbar showing up right above the keyboard. That toolbar should be hidden underneath the keyboard. It is pushed up each time the keyboard popups up. I've also attached below a second screenshot showing the normal screen when no input is active.
For Android, I had the same issue, and this posting fixed the issue: https://groups.google.com/forum/?fromgroups=#!topi
Is there something similar in the PlayBook WebWorks framework that makes sure the keyboard can be overlayed?
I've attached at the very end my index.html. Am I doing something incorrectly with the viewport information line?
<title>TouchTax - Mobile Tax Code and Regulations</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf8"/>
<meta name="apple-mobile-web-app-capable" content="yes"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"/>
<body onload="init()" class="enyo-unselectable">
<script> new App().renderInto(document.body); </script>
10-12-2012 09:25 PM
My guess is that your bottom toolbar is positioned using absolute css positioning. It is also probably absolutely positioned based on bottom: 0; as opposed to top: 550px.
I did a quick test and changing the div positioning from bottom to top should prevent the div from jumping up when the keyboard is displayed.
Let me know if this works for you.
P.S. Your app looks great!
10-13-2012 10:55 AM
Thanks James! You are probably right. I haven't changed the code yet because it was a pain to get that bottom bar to be at the bottom... more difficult than I think it should be! I'll try it in my next version.