-
Notifications
You must be signed in to change notification settings - Fork 51
Doesn't work with Firefox 77.0.1 #80
Comments
Same here. |
Consider using Stylus and GitHub Dark UserCSS https://github.com/StylishThemes/GitHub-Dark#installation You will have a better OOBE that way its more customizable and less buggy and includes multi @-moz-doc rules support for other GH sites, something the script cant. |
Thanks, works with Stylus. |
I mean if you are going to say you support other methods of using darkmode, then saying "use another program and it will fix the issue" is not a solution.
|
Works fine for me in Firefox 78 with Violentmonkey. No idea what could be causing it except a breaking change in Tampermonkey. Do you see any errors from the script in either the devtools (F12) or browser console (CTRL-Shift-J)? |
If you prefer not to switch or even try that's your choice. =) Read #73 (comment) and GHD has also dropped grunt to mention a few which the script never caught up with. I'm merely suggesting that you would have a much better user experience with stylus and GitHub Dark usercss This is a fact.- its updated almost daily.. With Script no matter what you still see flashes of white when loading pages even when this script was working very well. @silverwind I think the script repo should be archived, it was made to support what usercss now supports and usercss supports this much better, besides no one is really maintaining it and its served its purpose, |
Yeah I think I tend do agree with archiving. The UserCSS version is superior in every way (same configurability and instant style loading). I don't really understand why the Userscript version is getting considerable usage still. |
it serves no purpose anymore see StylishThemes/GitHub-Dark-Script#80 (comment)
I have two main devices: my PC and my laptop. Both have Windows installed.
On my PC, I remember Github dark broken a while ago, but on my laptop the script got broken after updating Firefox to 77.0.1.
I tried re-installing the script and even re-installing Tampermonkey, didn't help.
The text was updated successfully, but these errors were encountered: