From 0efcfc52f04ec4a3fa929868ad92096c9c7efe01 Mon Sep 17 00:00:00 2001
From: Lucas Winther <lucwin@ece.au.dk>
Date: Sat, 15 Aug 2026 01:43:47 +0200
Subject: [PATCH] fix: tell Dark Reader this page is already dark
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Dark Reader inverts an already-dark palette, which wrecks the interface: the
colours here carry meaning — the urgency ramp is how you read how soon
something ends — so having them re-mapped is not a cosmetic problem.

darkreader-lock is its documented opt-out. color-scheme: dark is the standard
signal alongside it, so browser chrome and form controls render dark too.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 index.html | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/index.html b/index.html
index 5e7255e..b2d5032 100644
--- a/index.html
+++ b/index.html
@@ -10,6 +10,22 @@
       content="Live and upcoming events across your gacha games, sorted by what ends soonest."
     />
     <meta name="theme-color" content="#12141c" />
+
+    <!--
+      This page is already dark. Two signals, because they cover different
+      readers:
+
+      color-scheme tells the browser (and well-behaved extensions) that a dark
+      rendering is intended, so form controls and scrollbars come out dark and
+      nothing tries to synthesise a light theme.
+
+      darkreader-lock is Dark Reader's documented opt-out. Without it Dark
+      Reader inverts an already-dark palette, which wrecks the urgency ramp —
+      the colours in this UI carry meaning, so having them re-mapped is not a
+      cosmetic problem.
+    -->
+    <meta name="color-scheme" content="dark" />
+    <meta name="darkreader-lock" />
     <link rel="preconnect" href="https://fonts.googleapis.com" />
     <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
     <link