You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a single bug. Do not report multiple bugs in one issue.
It's a frontend issue, not a backend issue; Otherwise please create an issue on the backend repo instead.
Summary
Text formatted as a code block has the white color scheme when using custom themes added into /lemmy-ui/extra_themes/
This occurs even if that custom themes just contains the same content as the default dark theme of darkly.css with no additional changes. Occurs in sidebar, posts and comments. Occurs regardless of browser/system's dark mode setting (separate issue mentioned here #2405).
Steps to Reproduce
Make a copy of darkly.css and rename it to something else
Place it in the /lemmy-ui/extra_themes/ folder where custom themes go
Navigate to account settings (ctrl+F5 for newly added file to appear)
The code-theming doesn't seem to work for custom themes. We'd need to add something to it that possibly checks the name of the theme, and makes sure it includes text like dark, to be able to set it correctly.
@dessalines Want me to move forward with the name checking approach? I can't see much of a way to handle this other than adding another option for themes to be light and dark, but that sounds like a lost more work.
Requirements
Summary
Text formatted as a code block has the white color scheme when using custom themes added into /lemmy-ui/extra_themes/
This occurs even if that custom themes just contains the same content as the default dark theme of darkly.css with no additional changes. Occurs in sidebar, posts and comments. Occurs regardless of browser/system's dark mode setting (separate issue mentioned here #2405).
Steps to Reproduce
/lemmy-ui/extra_themes/
folder where custom themes goTechnical Details
Firefox on Linux and Android
Lemmy Instance Version
0.19.4
Lemmy Instance URL
https://lemmy.zip/c/[email protected]
The text was updated successfully, but these errors were encountered: