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
Doxygen site: forced dark mode has bright white table of contents in Firefox #14873
Comments
The table is created with commands like this:
I must admit that I don't actually know where the
What is the usual way one defines things so that they show up right in all modes? I'm showing my full ignorance of web page design here :-) |
I'm also ignorant of these intricate web design details, but thankfully I have smart and talented friends like @pridgey who understand these things very well and figured all of this out. The issue is that Doxygen's default, which handles dark mode behavior with Without deleting the current intended light mode behavior specified in
I'm happy to throw a PR in for option 1 since it's an easy fix, but if you want something more like option 2, I'll let you handle it (unless you like the random colors I threw together in 5 seconds 😛 ) |
To me, the first version looks good. |
I'm preparing for a meeting now, but I'll throw a PR in later this afternoon if there aren't any objections :) |
Very cool -- I too love that I have friends who know who to talk to about stuff I have no idea about! |
While looking at step-64, I noticed Firefox was trying to force dark mode on the current Doxygen site. It almost works, but the table of contents does not enter dark mode.
Steps to reproduce:
I know website UI issues are often nasty to reproduce, but I think it's as simple as just changing this Firefox setting
Technically I noticed it first by using the "Firefox Theme" setting, but in my case it really just sets me to dark mode. I don't know how these forced dark mode compatibilities are handled, and I don't know if it's a big priority, but I thought I'd point it out in case others experience the same issue.
The text was updated successfully, but these errors were encountered: