Bug 1812840 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

So my Ubuntu default-theme and Alpenglow are both specially-able-to-reproduce-this because their `SelectedItemText` is different from the default text color.

And fortunately, we do correctly specify the proper contrasting background color in the relevant spot where we ask for `SelectedItemText` here (in the rule quoted in comment 10).

But that doesn't account for the possibility of having a descendant which **uses our `color`** but **is positioned over a different background area** (as this group header is, via `position:absolute; top: calc(-1.27em - 2px);`)

So that's how we got into trouble here.

Anyway -- manually setting `color` on the group header to the value-that-we-would-be-inheriting-when-our-parent-isn't-focused (as Dão's patch does) seems like it does address this problem and avoids the issue.
So my Ubuntu default-theme and Alpenglow are both specially-able-to-reproduce-this because their `SelectedItemText` is different from the default text color.

I was worried that maybe we had some CSS rule that was specifying this as a `color` without specifying the proper/contrasting `background-color` -- but fortunately we're OK on that front -- we do correctly specify the proper contrasting background color in the relevant rule (quoted in comment 10).  The issue was just that this `color: ...; background-color: ...` combination doesn't account for the possibility of having a descendant which **inherits our `color`** but **is positioned over a different background area** (as this group header is, via `position:absolute; top: calc(-1.27em - 2px);`)

So that's how we got into trouble here.

Anyway -- manually setting `color` on the group header to the value-that-we-would-be-inheriting-when-our-parent-isn't-focused (as Dão's patch does) seems like it does address this problem and avoids the issue.

Back to Bug 1812840 Comment 11