Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
Its almost like clicking the button causes a UI thread to call a javascript thread and the UI thread is locked out until the javascript thread has finished its job. If this lock lasts for more than a few milliseconds it kills the application. I've got no idea how things are architected under the hood but this seems to be whats happening for me :-S
Thanks for the feedback. This is very interesting and I hope RIM provides a solution or sheed some light on how to work around this. Otherwise, I feel that we are very limited on the apps that we could do with HTML/CSS/Javascript for Blackberry/Playbook, not complex and rich apps but just very simple ones.
What i'm finding annoying is that is OS5 this stuff all works and you can do some more complex applications but when porting it to OS6 its feeling rather flakey to me...... Theres a big shift in that Google Gears in OS5 is all synchronous in execution but OS6 forces you down the asynchronous path by only providing the asynchronous database access .... and this latest issue where onclick events seem to have to complete in milliseconds or you app gets chopped down as being unresponsive ... Urgh!!
Any idea on how long does it take for an issue to be looked? I entered the issue as suggested on this thread on 3/16 and it is still unassigned to a resource for analysis.
What is the ID of the issue you submitted into Issue Tracker?
Great thanks! I am assuming that the ticket will eventually get update. as of now, it still has the status of triage and unassigned. Also the thread from ingybing can be helpful for the development team, he provided a lot of feedback on his case for the same error message:
