Closed
Bug 1702899
Opened 5 years ago
Closed 4 years ago
White-on-white text in <input type="date"> popup in Dark Mode, if widget.macos.respect-system-appearance is true
Categories
(Core :: Widget: Cocoa, defect, P2)
Core
Widget: Cocoa
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | verified |
People
(Reporter: mstange, Assigned: bugzilla)
References
Details
(Whiteboard: [mac:darkmode][mac:mr1][proton-cleanups])
Attachments
(2 files)
Steps to reproduce:
- Set
widget.macos.respect-system-appearancetotrue. - Set the system theme or the Firefox theme to dark.
- Load
data:text/html,<input type="date"> - Click in the text field to open the date panel.
Expected results:
The contents should be readable.
Actual results:
White-on-white unreadable text
| Reporter | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Severity: -- → S2
Priority: -- → P2
Updated•4 years ago
|
See Also: → https://jira.mozilla.com/browse/FIDEFE-1728
Whiteboard: [mac:darkmode][mac:mr1] → [mac:darkmode][mac:mr1][proton-cleanups]
| Assignee | ||
Updated•4 years ago
|
Assignee: nobody → htwyford
Status: NEW → ASSIGNED
Iteration: --- → 90.3 - May 17 - May 30
Points: --- → 2
| Assignee | ||
Comment 2•4 years ago
|
||
This patch also removes the --default-arrowpanel-* variables. The only place they were used (ever?) was the datetime picker. Tim, I'm not sure of your level of involvement these days, but I'd be grateful if you could take a look seeing as you're both a themes expert and a Mac user.
Pushed by htwyford@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3ffdff1b7e43
Support dark datetime pickers on macOS. r=desktop-theme-reviewers,dao
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
Updated•4 years ago
|
Flags: qe-verify+
Comment 6•4 years ago
|
||
I have reproduced this issue using Firefox 89.0a1 (2021.04.03) on macOs 11, dark mode ( widget.macos.respect-system-appearance = true) .
I can confirm this issue is fixed, I verified using Firefox 91.0a1 and 90.0b4 on macOS 11.
You need to log in
before you can comment on or make changes to this bug.
Description
•