145200 - Up/down button in scrollbar not updated (depressed) when mouse pressed.

Status: RESOLVED EXPIRED

(SeaMonkey :: Location Bar, defect)

Description

[Mikko Virkkilä]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020510
BuildID:    2002051009

When you type the first few letters of an url, autocomplete drops down the list
to show you options. If there are many options the list you can scroll up and
down through them by using the vertical bar, pressing the arrows up and down,
this will let you scroll lower on the list. 

The image of the button is however not updated when you click on it.

Reproducible: Always
Steps to Reproduce:
1.Browse around UserFriendlys comic archive for a while
2.Go to slashdot
3.Now start tyoeing an url of one of the pages you visited in UserFriendly
archive ( http://ars.userfrie... )
4. When the list pops down, click on the scrollbar's down arrow.

Actual Results:  The arrowbutton remains the same, pressed or unpressed.

Expected Results:  The arrowbutton should be painted as pressed, just like any
other scrollbar arrowbutton.

Comment 1

[R.K.Aa.]

WFM trunk 2002051604, XP, modern theme.
Reporter: Which theme(s) are you seeing this with?

Comment 2

[R.K.Aa.]

i take that back. Testing on a day old CVS, linux: no hightlight if the dropdown
"triggered itself" as a result of typing there.

Comment 3

[Mikko Virkkilä]

I've tested it with both Classic and Modern and it exists in both.

There is a related bug: if the dropdown should display many (much more than a
100) links, the scrollbars' scrolling button (the thingie that is between the
arrow buttons and goes up and down) disappears and is replaced by a single light
dot. I have only seen this bug once and not been able to reproduce, hence no bug #. 

Comment 4

[Mikko Virkkilä]

This also happens with windows builds, so I'm marking this OS: Linux -> All

Comment 5

[Michael Lefevre]

seeing this in 2002112607/trunk/win2k, so marking confirmed.

Comment 6

[Mats Palmgren (inactive)]

Bug still occurs, Mozilla 2004-01-02-06 trunk Linux.

Comment 7

[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 8

[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