-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[stable28] fix(theming): Apply same logic on capabilities for primary color as done on themes #43032
Conversation
For my understanding, why not adjust this in server/apps/theming/lib/ThemingDefaults.php Lines 508 to 510 in 64ccc1e
🤔 |
Better would be in For a general fix I currently prepare this one: #42977 |
This comment was marked as resolved.
This comment was marked as resolved.
f70a37b
to
d2d5e7d
Compare
This comment was marked as resolved.
This comment was marked as resolved.
… on themes Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
d2d5e7d
to
afa56bb
Compare
cypress unrelated |
Summary
On themes we replace the default color with the accessible color, so we also need to do this on the capabilities.
This worked previously but as we now enforce contrasts of the text color clients that use the capabilities changes to black text on that color.
Checklist