-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Title Logo is Not Visible on Dark Mode #9814
Comments
omkarjagtap2212
changed the title
Title Logo is Not Visible on Dark Modebehavior Theme
Title Logo is Not Visible on Dark Mode
Jan 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which packages are impacted by your issue?
@graphql-codegen/client-preset
Describe the bug
When the system is configured to use dark mode as the default preference, an issue arises with the visibility of the logo in the title. In this scenario, the logo is significantly less visible, impacting the overall user experience. This issue needs attention to ensure optimal visibility for users who prefer dark mode. If necessary, additional text or elements may be considered to address this visibility concern effectively.
20240111181731.mp4
Your Example Website or App
https://the-guild.dev/graphql/codegen
Steps to Reproduce the Bug or Issue
1.Navigate to the website.
2.If your system is currently configured to use light mode, proceed to step 3.
3.Access the settings and switch to dark mode.
4.Upon transitioning to dark mode, observe the logo visibility concern on the website.
20240111181731.mp4
Expected behavior
When utilizing the website in dark mode, the background or color of the logo should subtly adapt to harmonize with the machine's default theme, enhancing the overall visual aesthetics and ensuring a seamless experience for users who prefer dark mode.
Screenshots or Videos
20240111181731.mp4
Platform
1.Operating System: Windows
2.Machine Version: Windows 11
3.Browser: Brave Browser and Google Chrome
Codegen Config File
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: