700246 - The color of some toolbar icons goes to white (inverted) with a dark persona

Status: RESOLVED FIXED

(Firefox :: Theme, defect)

Description

[Ferenc Magyar]

Attachment: ff_icons_bug.jpg

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

Apply a dark colored persona, for example: http://www.getpersonas.com/en-US/persona/44305


Actual results:

The color of some icons on the toolbar (open new tab, group your tabs, list all tabs) goes to white (inverted). See the attached image.


Expected results:

The color of the above listed icons should stay in default color after applying a dark colored persona.

Comment 1

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

I only see this when those buttons are housed on the navigation toolbar. On the tab toolbar, they all stay the same color.

Comment 2

[ffextensionguru]

This is normal behavior per Bug 671553

Comment 3

[ffextensionguru]

However, I should add that this is not ideal and looks goofy. I did create a stylish script [http://userstyles.org/styles/56094/firefox-8-un-white-toolbar-buttons?r=1320900717] to 'fix' this. However, it does not restore the actual button or glow effect though

Comment 4

[Stephen Horlander [:shorlander]]

(In reply to Al Hutchison from comment #2)
> This is normal behavior per Bug 671553

All the icons not living in a button should either be normal or inverted depending on if the persona is light or dark. So having two icons randomly inverted is not intended.

Comment 5

[Siddhartha Dugar [:sdrocking]]

Using a build with Bug 735691 fixed, on the default theme with tabs on bottom the panorama button in the nav-bar stays dark instead of being inverted. This needs to be fixed.

Comment 6

[Siddhartha Dugar [:sdrocking]]

(In reply to Siddhartha Dugar [:sdrocking] from comment #5)
> Using a build with Bug 735691 fixed, on the default theme with tabs on
> bottom the panorama button in the nav-bar stays dark instead of being
> inverted. This needs to be fixed.

Bug 679801 fixed this!