Nginx Rejects Dark Mode Support For Error Pages
Nginx Rejects Dark Mode Support For Error Pages
Not the news I was ever expecting to hear about but there you have it.
Good. You can already do this via custom pages. Leave the bloat out.
Respecting one of the most basic and simple browser preferences is definitely something we should expect a web server to be able to do. Not every developer will create custom pages, which is also an incredibly stupid solution for such a simple feature, so for users who may eventually see this page, it should simply respect what they have set in their browser.
From another reopened MR:
These accessibility changes constitute a net increase of 52 bytes on the affected response payloads.
Response download timing increase impacts at low network speeds:
- 7 milliseconds at 56 kbps
- 0.4 microseconds at 1 Mbps
Tell me again, how exactly is this bloat? Is anything more than "Hello, World" too much for you?
There really is no reason not to merge this.Thanks for replying, instead of just downvoting!
I think the bloat is not (primarily) in the end users experience, but in the extra code that the nginx maintainers must now continue to support, test, etc on an ongoing basis, which is not core to its function as a http server and proxy.
To me, this change goes against the Unix philosophy of simplicity, modularity, and the idea that programs should do one thing well.
Nginx should not contain logic that is not expressly related to serving or proxying web requests. The content it serves is up to the end user.
If we accept this change, should they also provide localized versions of all the error pages, too? I’m happy if their responsibility ends at just serving the content I provide.