Repository navigation
Feature Request: Dark Mode 🕶 #457
Description
I switch between over a dozen applications on my desktop every day. All of them are in dark mode ⬛. Then finally when I want to delight in the delicious offerings of the ytsync gods, BOOM 💥, my eyes suffer the disaster of a white screen ⬜. Please help save pupils 👁 from their demise. ☠
Thank you for your considerations 🤘
Activity
bwt615 commentedon Feb 5, 2024
Noir (and I'm sure other browser extensions) do this fine. I wouldn't waste time developing.
zuble commentedon Feb 25, 2024
Dark Background and Light Textextension for firefox
dcronin05 commentedon Dec 8, 2024
Or rather don't develop in light mode to begin with. Dark should be the default and let people use extensions to make it light if they want.
meeb commentedon Dec 9, 2024
If and when I ever get around to upgrading the interface to use Bulma it'll automatically gain dark and light theme support. That's a significant amount of work though and it's not especially high on the list.
tcely commentedon Feb 9, 2025
For anyone who wants it, your browser can use the styles from #254 to apply a darker mode.
Using Stylus and the contributed "Dracula Theme for TubeSync" user style.
StefanCodes commentedon Nov 14, 2025
@meeb I'm interested in taking on this task and played around with it a bit the last couple evenings.
A few questions:
meeb commentedon Nov 26, 2025
@StefanCodes thanks for taking an interest and sorry for taking a while to get back to your question. The plan is still generally to migrate to Bulma, however as this is a significant amount of effort for limited gain (and automatic dark mode) it's not been that high up the list for me to spend time on. The general drive for this was just to get some additional UI features and dark mode combined with Materialize no longer being maintained. It's not critical that a CSS framework has maintenance of course, but at some point there will be some issues with modern browsers and 7-8 year old CSS that causes problems.
I don't particularly have concerns about updating the templates, there's basically no JS in the current front end so it should just be a general slog of updating all the templates and fragments with no risk of esoteric JS stuff exploding.
My only concerns would likely be around the required tooling and dev process for Bulma 1.0 given it's incompatible with django-sass and requires Dart Sass. There's a few experimental Dart Sass Django packages but nothing like the previous stability of the libsass based packages. I wouldn't be too keen on having to bundle 100+mb of Sass nonsense just to get some CSS to display properly.
However, if your plan is to just use the minified bundled Bulma that might work. Any complex styling might be an issue though as that would suddenly devolve into Sass-land.
Edit: for my part, I was waiting for a sane, small and library based Django Dart Sass package first that didn't just wrap
sassin a subprocess or other hacks.StefanCodes commentedon Dec 23, 2025
Gah, sorry @meeb - apparently my notifications are turned off for this repo!
I have a branch that's working quite well. I'll spend a little more time on polish and post a draft PR and see if any contributors can give it a quick sniff test!
meeb commentedon Dec 24, 2025
Thanks! As this is likely to be a massive change feel free to just link your branch for now and I'll take a peek. I imagine the draft PR is going to be massive if you've rewritten every template.
StefanCodes commentedon Dec 28, 2025
@meeb oh dear, it is rather large 😆
I have a draft PR here with a few inline comments: #1353
Happy to receive any early feedback on approach!