03-03-2010 11:52 AM
We just downloaded the new Widget Beta 3 SDK and are adding Focus based navigation to our Widget.
Some notes about the Widget:
- lots of html elements (div, button, input, img etc)
We have followed the RIM documentation on focus based navigation, and initially it seems to be working fine in the Widget. Navigation between the different elements works and they are properly highlighted. Then suddenly after clicking around, the Widget and the device itself totally hangs. It is probably the UI thread hanging, since the Widget seems to continue sending ajax requests (we can see the 3G traffic arrows in the upper right corner now and then). But the device does not respond to any button clicks.
We leave the device, after ~30 minutes there is a popup shown with the following message:
Uncaught exception: Application focus(176) is not responding; process terminated"
Focus based navigation is a requirement in our application. We urgently need help on this issue (probably from the RIM developers!), since it might prevent us from using the Widget environment. I realize it is hard to pinpoint the error with the information above, let us know and we can send you some code!
03-03-2010 02:52 PM
I've passed this to the development team. Any chance you could send us some HTML that would replicate the issue?
03-04-2010 08:30 AM
Tim - I have sent you a private message with some download instructions for your team.
We have now created a dummy Widget which can trigger the error. This Widget uses jQuery for DOM manipulation, that way we can reproduce the error every time. The error comes when we use focus based navigation, the user clicks an html element and our click handler performs show/hide operations.
We suspected jQuery caused the error, so we rewrote our application to handle all DOM manipulations (show/hide etc) without jQuery. Unfortunately that did not solve the problem, it still happens but not as frequently and we can not see any pattern how to reproduce it.
03-04-2010 08:39 AM
Thanks for the PM.. I have sent it to our development team for them to investigate
03-19-2010 08:34 AM
Do we have any progress on this issue from RIM developer team? Seems similar problem has been reported in other posts at the forum as well. It´s sort of a stopper for us...
05-04-2010 11:11 AM
05-06-2010 07:42 AM
I heard some positive news on the work being performed towards a fix to this issue.. We are running through the scenarios to see if our fix solved all aspects of the problem.
05-10-2010 01:57 PM - edited 05-10-2010 02:26 PM
I'm wondering if what I'm seeing is the same problem (and hopefully same eminent fix....):
I have a table with 'hover' effects on the table data and 'x-blackberry...' extensions to catch the up/down focus navigation (so I can direct the next focal point per my desires).
(As an aside, sometimes the CSS hover effect gets left behind on an element that is no longer in focus -- so I have two table data elements showing the hover effect...)
The user does an action to that will add a row to the table after an AJAX interaction (currently I'm simulating the AJAX interaction with a setTimeout-run routine). If, after kicking off the asynchronous action that will ultimately manipulate the DOM, I then use the trackback to move the focus around then I often will get the typical frozen Blackberry (no input works except the End/hang-up key; and get a pop-up about non-responsive thread upon power cycle of the device via the End key). This freezing of the device seems to correspond with when the timer kicks off and starts manipulating the DOM.
Seem to be the same issue?
05-10-2010 02:21 PM
This is the issue that we are concentrating on.