-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
Dark mode toggle hover and transparency issue #241
Comments
I'm not following, what exactly is the issue? Perhaps providing a screenshot of what you think is wrong would help. |
Ah, some of this appears to be the result of #237 combined with some issues from the Darkmode.js 3rd party library. |
Could you provide your browser version? I can't reproduce it. |
It seems unrelated, but I can fix it. |
It's directly related. That PR is where the opacity was introduced, and the opacity is exactly what is causing the button color to change as you scroll the page. |
I tried to remove the opacity, but the problem persists. The button on the official website also have the problem when using a light background. |
I'm not refering to the black edge that's peaking out. If you read my original message that you quoted, I do say the reported issues are a combination of that PR and some existing issues in the library itself. The concerns mentioned about the background are the result of the opacity changes. The black edge poking out is from the library. |
Yes, you are right. Adding background-color instead of the opacity might fix it. |
Awesome! |
When you hover over the dark mode button when in light mode, there are two very slightly different colors: #210d26 and #000000. The dots on the light mode background are slightly lighter than the background of the button. Also, the white part of the button that sits on top of the black background that expands into dark mode when the button is pressed is slightly misaligned. I spent some time trying to fix this but I don't know anything about html or css.
The text was updated successfully, but these errors were encountered: