Web and WebWorks Development

[andyjgibbs]

I am experiencing a strange issue with a BlackBerry WebWorks app that I developed.  The issue is occuring on BlackBerry devices that have a virtual keyboard such as the Torch.

When the user focuses on a textfield, causing the virtual keyboard to pop-up, and the user subsequently scrolls down the screen while the virtual keyboard is open, and finally, the user closes the virtual keyboard, the controls on the screen lose their click position.  After this occurs, in order to click a control such as a texbox, dropdown box, or button, the user needs to click further down the page and not where the control is actually situated.  Also, it is not possible to scroll back up to the top of the page once this occurs.

I have tried numerous workarounds such as restricting meta viewport tag and tried to use javascript to auto-scroll back to the top after a textfield is updated - but the issue is still occuring.

This appears to be a bug in the BlackBerry WebWorks framework.

Has anyone experienced this issue?  Can you advise of any solutions or work arounds?

Thanks

[andyjgibbs]

I am using version 2.3.1.5 of the WebWorks framework; the most recent version as of this posting.

[shanesmith]

I've experienced this bug to, also with the latest WebWorks framework.

[shanesmith]

Created an issue in the GitHub repo for WebWorks

https://github.com/blackberry/WebWorks/issues/116

[bbkeeper]

While waiting for the fix, i suggest you guys using css "position: fixed" for the components and bind those components against "top" like:

.yourComponent{ position: fixed; top: [distance to top];}

Hope this helps.

[shanesmith]

Setting the position to fixed does not fix the problem.

I'd like to point out that it's not an HTML positioning problem but rather what seems to be a WebWorks screen drawing bug as the items get moved up, but the interactions (such as tapping) need to be done in their original position.