It doesn’t need any CSS since the Nginx error pages use the browser’s default styling. The meta tag just tells the browser to use its default light or dark mode styling depending on the user’s preference.
A standard behaviour on all sites that properly implement dark mode is that it adheres to the system-wide dark mode setting by default. If the user doesn’t want dark mode, they’d turn it off system-wide. The site can let the user opt in to dark mode just for that site, but the default is based on the system setting.
And some css, and accessibility issues. Dark mode isn’t actually great for everyone.
It doesn’t need any CSS since the Nginx error pages use the browser’s default styling. The meta tag just tells the browser to use its default light or dark mode styling depending on the user’s preference.
A standard behaviour on all sites that properly implement dark mode is that it adheres to the system-wide dark mode setting by default. If the user doesn’t want dark mode, they’d turn it off system-wide. The site can let the user opt in to dark mode just for that site, but the default is based on the system setting.
You didn’t actually check, did you?
Yes, I checked the pull request: https://github.com/nginx/nginx/pull/567/files and I’m also a web developer so I understand how it works.
I just started an nginx instance, made a web request and poof: css.
But that is a good idea to fix tho
Check what? They’re right.
🤡
Respecting the user’s choice (whether to use dark mode or not) helps accessibility rather than hindering it.
Unfortunately most devices and some browsers nowadays aren’t great at that. The web browser and the nginx error pages would just follow.
But that is an issue to be addressed elsewhere, to be fair