User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+ Build Identifier: Thunderbird Nightly: Linux, GTK, version 1.0+ (20050528) If one has enough local folders, the destination list for &Message->&Move/&Copy is taller than the visible screen area. Navigating with Keyboard-UpArrow/DownArrow, the highlight cursor disappears off screen at the top or bottom of the visible menu. Instead, the menu MUST scroll to keep the selection highlight visible. NICE-TO-HAVE would be a pref establishing the top/bottom margin where scrolling triggers, defaut 0-px I suppose. This would allow to make visible the "next" selection in cases where one is unsure the desired target exists. NOTE: The MOUSE does make the menu scroll. This bug relates only to keyboard handiling. Reproducible: Always Steps to Reproduce: 1. Create at least 30 local folders at the same level -- that should be enough to exceed screen height. 2. Select or open a message, execute &Message->&Move and attempt to select the destination folder using the keyboard arrow keys. 3. Actual Results: At the top or bottom of the visible menu, the selection highlight disappears off screen and there is no way to know what one is selecting. Expected Results: The menu should be scrolled to keep the selection highlight visible.
SAME SYMPTOM also noticable in FIREFOX, Context Menu. The C/M is not taller than the screen -- although I've seen it that way with enough extensions; however it is of some limited vertical size and the selections are greater than that. The menu has teeny-tiny scroll arrows at top and bottom. However, keyboard navigation does not trigger scrolling. Mousing does. DITTO Firefox Bookmarks menu which is too tall for the screen.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.