Improve macOS control colors
Categories
(Core :: Widget: Cocoa, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: sam, Assigned: sam)
References
Details
Attachments
(1 file)
Some colors (Infotext
, Menutext
, and MozSidebartext
) are set to NSColor.textColor
instead of NSColor.controlTextColor
, which is the color observed in native controls.
When these values were originally selected in bug 517412, the system colors were the same, but they have since diverged.
Assignee | ||
Comment 1•7 months ago
|
||
Instead of NSColor.textColor, use NSColor.controlTextColor, which is the color observed in native controls.
When these values were originally selected in bug 517412, the system colors were the same, but they have since diverged.
Updated•7 months ago
|
Pushed by bwerth@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d95b94d4f547 Improve macOS control colors. r=mac-reviewers,bradwerth
Comment 3•7 months ago
|
||
Backed out for causing wpt failures at /css/css-color/deprecated-sameas
Backout link: https://hg.mozilla.org/integration/autoland/rev/1f9c7ba2aa71e5715e14177e0fac7a6e1de48698
Assignee | ||
Comment 4•7 months ago
|
||
It looks like both InfoText
and MenuText
should always match CanvasText
, at least to web content, per the latest spec.
CanvasText
uses the default color, rather than an OS-provided value. That seems incompatible with using OS-provided values for either InfoText
or MenuText
within web content.
Assignee | ||
Comment 5•7 months ago
|
||
(In reply to Sam Johnson from comment #4)
It looks like both
InfoText
andMenuText
should always matchCanvasText
, at least to web content, per the latest spec.
CanvasText
uses the default color, rather than an OS-provided value. That seems incompatible with using OS-provided values for eitherInfoText
orMenuText
within web content.
There is existing infrastructure to provide stand-ins to web content, which is already used to make WindowText
also match CanvasText
. Using stand-ins for InfoText
and MenuText
as well should resolve this.
Assignee | ||
Comment 6•7 months ago
|
||
(In reply to Sam Johnson from comment #5)
(In reply to Sam Johnson from comment #4)
It looks like both
InfoText
andMenuText
should always matchCanvasText
, at least to web content, per the latest spec.
CanvasText
uses the default color, rather than an OS-provided value. That seems incompatible with using OS-provided values for eitherInfoText
orMenuText
within web content.There is existing infrastructure to provide stand-ins to web content, which is already used to make
WindowText
also matchCanvasText
. Using stand-ins forInfoText
andMenuText
as well should resolve this.
I've decided to revert this approach and instead annotate the failures on Mac. These tests already fail on other platforms for the same reason it now fails on Mac, and using stand-ins has consequences for the non-native theme.
Comment 7•6 months ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:sam, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
Comment 8•6 months ago
|
||
(In reply to Sam Johnson from comment #6)
I've decided to revert this approach and instead annotate the failures on Mac. These tests already fail on other platforms for the same reason it now fails on Mac, and using stand-ins has consequences for the non-native theme.
That seems fine, too. I will obsolete the patch for you, to prevent Bugzilla from pinging us with reminders.
Updated•6 months ago
|
Comment 9•6 months ago
|
||
I'm confused, Sam updated the patch that you marked as obsolete with the approach described in comment 6. It was just waiting for review aiui.
Updated•6 months ago
|
Comment 10•6 months ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #9)
I'm confused, Sam updated the patch that you marked as obsolete with the approach described in comment 6. It was just waiting for review aiui.
I apologize. I am obviously being the source of the confusion. I've un-abandoned the revision (though I did commandeer it, so sam will need to take it back) so hopefully we're back on track. I'll stay out of it now.
Comment 11•6 months ago
|
||
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f78d4c24f10a Improve macOS control colors. r=mac-reviewers,emilio
Comment 12•6 months ago
|
||
bugherder |
Description
•