Closed Bug 228869 Opened 21 years ago Closed 20 years ago

dropdowns skip/jump every other entry when using up/down keypresses

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 219706

People

(Reporter: calum.mackay, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031218 Firebird/0.7+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031218 If I use the keyboard to move up and down a dropdown menu, e.g. the From identitiy when composing, or the Views dropdown, the highlighted selection skips every other entry, moving up and down two entries at a time. It's bizarre. Reproducible: Always Steps to Reproduce: 1.bring up a dropdown menu 2.press down arrow key repeatedly 3. Actual Results: selection moves down two entries at a time Expected Results: selection should move down one entry at a time This has been around for a little while, although I only notice it occasionally, normally using the mouse. I searched all open mailnews bug summaries, but didn't see anything obvious for skip, jump or dropdown. Hope it's not an obvious dupe.
I'm running my own GTK2 build.
Confirmed. This happens on the mail client only, but not on the browser location bar pulldown which does move up or down by one list entry.
I can confirm that this also happens on my Solaris gtk2 build but NOT on my gtk1 build of mozilla. This appears to be gtk2 specific. The earliest build i have verified it on is 20031217
I had a really old build lying around, from 20030530, and the bug is present there, too.
This appears to be fixed by the checkin yesterrday for bug 219706 Reported please close.
Yup, this should be a dup, thanks Mitch. *** This bug has been marked as a duplicate of 219706 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
and the fix for 219706 does indeed fix the problem I reported. v.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.