Closed Bug 1390929 Opened 7 years ago Closed 7 years ago

Firefox 55.0.1 ignores optgroup background colors

Categories

(Core :: Layout: Form Controls, defect)

55 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1388682

People

(Reporter: dougpgibson, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 Steps to reproduce: Went to a website that has a select element with an optgroup that has a background color and noticed the background color was not the correct color (works correctly in IE 11 or Chrome). EX: http://mfvx.marketfronts.com/test-v1/optgroups.asp This was also reported in bug id 1386174 for DevFox 55.0b13 (64-bit) 15 days ago and was apparently ignored. https://bugzilla.mozilla.org/show_bug.cgi?id=1386174 Web developers don't appreciate rendering issues like this, especially ones that have been reported prior to official release of an firefox update. Actual results: Firefox ignores the set background color and uses #FOFOFO instead. Expected results: It should display the background color that is set in the css or element.
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
What I see is that 55 draws the yellow background color behind some options in http://mfvx.marketfronts.com/test-v1/optgroups.asp, and in 54 they are all grey. Did you perhaps not get e10s with 54 and with 55 you got e10s? non-e10s and e10s selects have different implementations.
No we are not talking about select options, we are talking about select optgroups. The optgroups are ignoring the background-color, as I said and as has been reported in bug id 1386174 for DevFox 55.0b13 (64-bit). Run the page in chrome or IE, you will see that FF displays all optgroups in #F0F0F0 regardless of the background color set. Does not happen in IE or chrome, and did not happen prior to FF 55.
is this bug 1388682? If so, should be fixed in Fx 55.02
(In reply to j.j. from comment #3) > is this bug 1388682? If so, should be fixed in Fx 55.02 Fx 55.0.2, sorry
It appears to be fixed in FF 55.0.2
thanks, most likely a duplicate then
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.