228948 - Scroll bars in composer address block don't work

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

Description

[Charles Schultz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208

The address block scroll bars in the Mozilla composer page don't function. When
typing in an address and the autofill feature provides more than one selection,
a drop down window with possible matches shows up. If there are more than four
selections, the dropdown window has a scroll bar on the right hand side.
However, when clicking on the scroll bar, the current selection is selected
rather than scrolling to additional selections.

Reproducible: Always

Steps to Reproduce:
1. Type a partial address in the address block of composer.
2. Have more than four possible matches.
3. Try to scroll to additional matches.

Actual Results:  
The current selection is selected rather than scrolling to additional selections.

Expected Results:  
Scrolled to show additional matches.

This used to work on an earlier release (pre 1.6?).

Comment 1

[dolphinling]

If you mean what you get when going into composer, inserting a link, and going
to the link location thing, then I can confirm this on Linux too.

I wonder if this has anything to do with the fact that the arrow for the
dropdown is strange...

Comment 2

[Scott Packard]

version 1.6b on Solaris 9 has exactly the same problem.
Let me elaborate.
Say I type "Eric", and I have auto-complete on and it queries a company LDAP
database and returns more than four possible matches.  A vertical scroll bar
appears, but if I try to single-click the down-scroll triangle, *boom*.
It chooses the first address and the scrolling disappears.  Auto-complete is
finished, as far as it's concerned.

Comment 3

[Scott Packard]

*** This bug has been confirmed by popular vote. ***

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420