GNOME Bugzilla – Bug 568158
Detailed where am I command very slow with Mozilla Thunderbird 3.X.
Last modified: 2009-11-09 21:35:39 UTC
Please describe the problem: Dear Developers! When I using Mozilla Thunderbird 3.x version and try execute detailed where am I command, the command execution is very slow. I using desktop keyboard layout. When launched the Mozilla Thunderbird application and try pressing two Insert+Enter key, nine second not happen nothing, and after this Orca sayes the required information, for example: You are online. Unread: 0 (the unread messages number). All: 450 (the readed messages number). Possible solving this problem? Attila Steps to reproduce: 1. Please launch Mozilla Thunderbird application. 2. Press two quickly Insert+Enter combination with desktop layout. 3. Actual results: Lot of seconds not happen nothing, Orca wait 9 second, and after this seconds elapsed, spokening the required informations. Expected results: Does this happen every time? Yes. Other information:
Getting this on our 2.26 radar screen. We *might* get to it, but we're not sure.
I can make this problem go away by searching objects from the bottom up. (As part of the current refactor of whereAmI, I am moving pretty much everything out of where_am_i.py. In doing so, I redid the method in question and it's quite snappy now. Ditto for the status bar in Firefox.) Therefore, assigning this to me. The fix will go in as part of the refactor, but I'll keep this bug open until then.
I forgot to close this one. The change I mentioned did indeed get included as part of the recent WhereAmI refactor. Still, to verify one more time that this bug was fixed, I opened my Gmail IMAP 'All Mail' folder which has 7780 messages, 2897 of which are supposedly unread. I maximized the Window in a 26-inch, vertically-rotated monitor which caused 93 rows worth of accesibles in the list of messages to be visible. When I pressed Insert Enter 2x quickly as described in the opening report, I immediately got the status bar information and no lag. For the record, the bugs upon which this bug has been marked as depending are still important/necessary. Were we looking for something which wasn't at the very top or very bottom of the hierarchy, the above test would still be quite slow and painful.