From 12b6544a7d1cd56bd9dcc4f08038b634dda43696 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Fri, 10 Jul 2026 01:04:56 +0000 Subject: [PATCH 1/3] Fix unreadable Xanga mobile-nav links caused by an overly-broad substring selector html[data-theme="xanga"] body a[class*="bg-accent"] was meant to fix contrast for links with a literal, resting bg-accent background, but [class*=...] does substring matching against the whole class string - so it also matched inactive mobile-nav links whose only accent-flavored class was the hover-prefixed "hover:bg-accent-orange", forcing dark --on-accent text onto them even at rest (on top of their actual dark navy background), making Home/Blog/Contact/Hub/Links/V2ME/Learning/Projects unreadable in the mobile menu. Excludes any element whose class also contains "hover:bg-accent" from this always-on rule, matching the same guard already used for the analogous hover-only overrides a few lines down. Co-authored-by: Thomas Bohn --- app/globals.css | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/app/globals.css b/app/globals.css index 11e61fc..59e59e4 100644 --- a/app/globals.css +++ b/app/globals.css @@ -270,15 +270,20 @@ html[data-theme="xanga"] body header nav a:focus-visible * { on top of that background. This is deliberately not scoped to "header" only: the mobile nav menu is a sibling of