Web and WebWorks Development

[tneil]

Hmm.. I'm wondering if it's a general trackpad/WebWorks issue... Have you tried to see if the same thing happens without bbUI? 

[nunodonato]

No, I didn't... my guess is that it would work. It seems bbui messes up the focus sometimes.

For example, to try to fix this problem, I tried to do a setFocus on a different element everytime the screen changes, but it doesn't seem to work.

The x-blackberry-initialFocus="true" also seems to break with bbui.

[songdawg]

I have also been having issues with setting focus to a text input while using bbui. In the screen's onload, setFocus or focus() doesn't seem to work. Would love to see a sample of it working.

[tneil]

You likely can't set the focus in the onscreenready event of bbUI.  This event fires when the screen has been loaded into memory so that you can manipulate it before it is inserted into the DOM.

I have an ondomready event that will be added and available in 2.5 weeks

[tneil]

Figured out the slow trackpad navigation issue in bbUI

https://github.com/blackberry/bbUI.js/issues/33

[nunodonato]

Cool!

Doesn't look so pretty, but the speed is way better

[liammccann]

This seems to be the same issue as: http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/bbUI-Input-Slow-Delayed-Issues/t...

Still find many problems with focus based navigation and input feilds. Major annoying delays.

[Wongadob]

I too am having really bad issues with focus based navigation and page switching. I have a seperate post for it, but it may be related to some of the isses above. I do not believe it is related to DOM ready as I can wait for ages afterwards and then try to set in web inspector console. It just wont set to new ID, but if I move the cursor once then do exactly the same thing to set the focus. It works.

Here is my post there is a lot of information in there

http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Can-t-get-focus-setFocus-working...

[liammccann]

Has anyone came up with a fix or solution for this issue yet? Or even a work arround?