Checkboxes and radio buttons do not respect SelectedText color in Windows 10 dark HCM
Categories
(Firefox :: Theme, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox122 | --- | wontfix |
| firefox123 | --- | wontfix |
| firefox124 | --- | verified |
| firefox125 | --- | verified |
People
(Reporter: tgiles, Assigned: emilio)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: access, regression)
Attachments
(2 files)
Haven't checked on Windows 11 as I don't have a machine for that yet, but our checkboxes and radio buttons do not change their color to the SelectedText system color and instead show the default primary teal color in Windows HCM dark themes. For some reason if I select Windows High Contrast White, the checkboxes and radio buttons use the SelectedText color. Not entirely sure what is going on in this case.
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1867769
:emilio, since you are the author of the regressor, bug 1867769, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Reporter | ||
Updated•2 years ago
|
| Reporter | ||
Comment 2•2 years ago
|
||
Not going to claim expertise here, but it looks like we're setting the SelectedItem color in the GenericDarkColor function to the primary teal color seen in the screenshot. Not sure how we would change this without potentially breaking the generic dark color for other platforms if I understand the code correctly.
| Assignee | ||
Comment 3•2 years ago
|
||
Really regressed by bug 1789214.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
This seems hard to reliably test... Basically, this forces all windows
HCM to use "light" system colors for non-native drawing, the same way we
do for system color resolution.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Emilio, can we please get Priority/Severity settings applied here?
| Assignee | ||
Updated•2 years ago
|
Comment 8•2 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
I was able to reproduce the issue on Win10x64 using Firefox build 122.0.
Verified as fixed on Win10x64 using Firefox build 124.0b2 and 125.0a1. (Checked that they are correctly displayed on Win11 also)
Description
•