-
Notifications
You must be signed in to change notification settings - Fork 0
feat: custom selection colors #192
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
Conversation
✅ Deploy Preview for cesium-hydrogen-new ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Oop- that wasn't supposed to happen. This was a weird one, since we had a custom "blue" color in Tailwind but there is already a "blue" color defined by Tailwind itself, on /about/become-a-collaborator the hierarchy was getting messed up and the text would show selected as orange instead of blue. To fix this I had to change the name of the color for our custom blue into something different, I thought "signature-blue" was okay. As for the text not turning orange in the case you mentioned, I have no idea why "selection:text-primary" does not override the default text-white, so to fix it I just changed it to a bg-white with opacity, which I think also looks good. Let me know what you think @joaodiaslobo 🙌🏼 |
joaodiaslobo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! ![]()

Closes #156