Closed plaskier closed 2 years ago
Before | After | Dark | Light |
---|---|---|---|
Font (and color) issues in each post may still exist, in mobile/desktop views.
Feedback for further improvement
* ~Theme toggling working on mobile FF, but not on desktop~ // may not work on old browsers * [ ] Font inconsistency in frontpage, /hkers, /c1, /c2, and posts * [x] Footer changes to be reconsidered
Trying to fix font color and font family issues by rewriting CSS files. CSS files are being rewritten by using variables instead of specific values in each CSS files.
The default font color and font families will be kept the same.
Dark theme button seems broken. Further debugging is needed. The dark theme still cannot be implemented.
By inspecting element, the problem occurs when the class
of <body
has both parameters, dark-theme
and light-theme
.
When both parameter exists, for example, if you are in system light mode, then you are most likely to have the web page set to dark mode. Therefore if now you change the system theme preference and set to dark mode, the web page would turn to an annoying light mode.
The solution is under development.
Make sense to extend design perspective to qualitative perspective. Well, I'd suggest squash merge first and release as a touchstone for this feature. Ongoing optimization may also include usability and user experience despite no rigid formula.
An attempt to import three condition of the toggle makes sense, which is auto, dark, and light.
In dark or light condition, user preference would override system preference. But if it is set to auto, then the system preference takes over. In this way the logic is much clearer.
The main script has been optimized. Now the issues is to decide where to put the button.
I believe now the dark mode could be implemented for using.
Now the decision logic for switching themes is like this:
@plaskier Great job! You have the access rights to manage this repo's issues and PR. Once this PR is (squash) merged, I can create a release then.