Back Forwards history drop down - arrows not correct design




11 years ago
8 years ago


(Reporter: bryansmiley78, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-15])



11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008032705 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008032705 Minefield/3.0pre

In the back forwards history drop down, when hovering over pages, back forwards arrows rightly appear, but in the incorrect back forwards design.  These were previously blue when they should have been green.  Now they are silver beaks.  Please resolve to correct, or at least close to correct, back forwards arrows for consistency.

Reproducible: Always

Steps to Reproduce:
1. Click back forwards history dropdown
2. Hover over entries
3. Notice incorrect arrow designs
The icons need to be easy to see given the various highlight colors, making white pretty much our only option.

Comment 2

11 years ago
Beaks only and colour white is correct yes, but as said, they're visibly silver at the moment, not white the same as back/forwards, as they should be.  
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.