My post on two-state dark mode toggles sparked a lot of discussion about the optimal dark mode toggle design. But should you have a (persistent) dark mode toggle at all? I have since been convinced that for most websites, the answer is no.
A toggle is not the best solution to your problem.
100% correct. Unfortunately I’m far more likely to have access to a toggle than for them to make their dark mode nice.
E.g. I’ve asked them to add more languages to the code button in their WYSIWYG editor for replying to tickets. I don’t use/do any web stuff but I had figured out that they use Froala, and Froala uses prism.js. I asked them to include 5 more languages (bash/sh/shell, batch, ini, json, Powershell) and requested that the list be sorted alphabetically, and told them it should just be a matter of changing the Froala codeSnippetLanguage plugin option. I haven’t even had a reply in 5 months.
I also spent some time trying to modify the WYSIWYG editor options myself using a userscript but didn’t get anywhere useful.
100% correct. Unfortunately I’m far more likely to have access to a toggle than for them to make their dark mode nice.
E.g. I’ve asked them to add more languages to the code button in their WYSIWYG editor for replying to tickets. I don’t use/do any web stuff but I had figured out that they use Froala, and Froala uses prism.js. I asked them to include 5 more languages (bash/sh/shell, batch, ini, json, Powershell) and requested that the list be sorted alphabetically, and told them it should just be a matter of changing the Froala
codeSnippetLanguageplugin option. I haven’t even had a reply in 5 months.I also spent some time trying to modify the WYSIWYG editor options myself using a userscript but didn’t get anywhere useful.