-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
Riverlea - merge crm-c-light-text and crm-c-text-light , tweak alerts in Hackney Brook dark mode #31994
base: master
Are you sure you want to change the base?
Conversation
🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷 Introduction for new contributors...
Quick links for reviewers...
|
a2d9bfe
to
4c5ee33
Compare
@ufundo thanks for spotting the The other main change here around warning colours will need some testing. Emphasis colours are a headache because there's so many different ways they're used and there always needs to be good colour contrast. E.g. for warning you get:
In short it should be a case of 'this is the red or green I want for danger/success' but in reality those colours need to work with the context and each stream has their own quirks. This is one of those problems I only realised while building RiverLea so it's ended up quite complex, and yet also not without issues. I tried to track this issue here: https://lab.civicrm.org/extensions/riverlea/-/issues/29 but as recently as v1.3 I had to add more emphasis colour variables to get the right contrast ratios, and I still occasionally find bugs, ie https://lab.civicrm.org/extensions/riverlea/-/issues/38, because of some combination, say, of an alert and an icon. All of which is to say a) I will test these alert colour changes in a bunch of contexts next week; b) if it doesn't break anything else - great - if it does, then c) maybe it would be good to have a call to see if there's a way to rationalise/simplify this all. Most sub-theme makers won't need this level of complexity/configurability (in the core variables file, there's 9 variables with 'success' in the name and 11 with 'warning' - almost all specifying colours!). |
hi @vingle thanks yeh I pulled a thread and... it kept going. Great if you can test a bit. Maybe a call would be good. I was thinking about streams and customised screens and how it would be really great if we can get as clearer view as poss of which variable pairs might appear as text-on-background or vv. But appreciate its not simple! I think the notification text disappearing in dark mode is a new example of the same bug For naming, sorry I didnt notice that convention. I thought
|
That makes sense. Flip side is being able to search FWIW - this screengrab doesn't occur for me, is it because of you forcing black on text in dark-mode standalone because of the login screen (#31991)? ![]() |
Overview
Merge eerily similar css vars, tweak alert colours in Hackney Brook dark mode.
Journey
There's two separate css vars but I think there should be one? @vingle unless I'm missing something?
I noticed this when looking at the Standalone login page on Hackney Brook with Dark Mode -- the alert message text color seems to be undefined, because it's using crm-c-light-text , which isnt defined in that context.
Updating the mismatch actually was a step back, so then following lead I was trying to rationalise how the alert colours work in Hackney Brook dark mode. My brain couldn't cope with e.g.
--crm-c-light-green
now being dark green and vice versa... so I thought as a general rule it might be better to keep those color vars the same way round, and flip where they are assigned to instead.They didn't seem to be used in too many places, so I this will make the alert colours and bit saner and not change much else?
Before
(The notification works a bit coincidentally, because the text color var happens to be undefined)
(note invisible alert text in popup)
After
(notification message fixed)
(no changes as far as I can see)
Comments
I haven't tested all the other streams extensively. It's definitely possible that there are other small issues from the merging. Seems like it would be a good PR to get in early in the alpha cycle...