352746 - Go, Search and Search Engine buttons do not give adequate visible response when a user clicks on them

Status: RESOLVED DUPLICATE of bug 417078

(Firefox :: Theme, defect)

Description

[ronin.achilles]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060914 BonEcho/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060914 BonEcho/2.0

There are four similar buttons on the Navigation toolbar. The addressbar dropdown, go button, search engine button and search button. Each of them have separate reactions to hover and click (pressed state). While the addressbar dropdown does have a subtle pressed state, the others have nothing thats visible to the naked eye.
All of these buttons should have visibly different states when normal, hovered and pressed. And these states should be the same across the four buttons.

Reproducible: Always

Comment 1

[Pam Greene]

(In reply to comment #0)
> All of these buttons should have visibly different states when normal, hovered
> and pressed. And these states should be the same across the four buttons.

I'd tend to agree about the three action buttons -- Go, Search, and the search engine button.  But I think it's fine if the dropdown control, which is really part of the urlbar rather than the broader toolbar, stays distinct.  In that case this request would be for more apparent hover and active states for the other three.

Comment 2

[Peter Kasting]

See also bug 352162 comment 14 onwards.

Comment 3

[ronin.achilles]

Attachment: Beta 2 vs Current Builds Comparison

Screenshot comparing the three states (Normal, Hover, Pressed) of Go button between Beta 2 and the latest Nightlies (going to be RC1).

The difference in 'Pressed' state is most pronounced and missing from the current builds.

Comment 4

[ronin.achilles]

Changing the Summary to limit the scope of this Bug to Go and Search buttons' 'Pressed' state.

Comment 5

[Biju]

what about hover effect on demo attachment 241607 [details] 

is this same as bug 355640?