From 90fbee4ef8adea052fc8efda07764ceb724e2131 Mon Sep 17 00:00:00 2001
From: saberzero1 <github@emilebangma.com>
Date: Sat, 14 Feb 2026 01:11:56 +0100
Subject: [PATCH] fix: use dangerouslySetInnerHTML for inline CSS to prevent
 HTML-escaping

Preact was escaping & characters in SCSS-compiled CSS (e.g. & nesting)
into &amp;, breaking CSS rules. Using dangerouslySetInnerHTML bypasses
the escaping, matching how browsers expect style element content.
---
 quartz/util/resources.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/quartz/util/resources.tsx b/quartz/util/resources.tsx
index 12dd77eee..43151d1b3 100644
--- a/quartz/util/resources.tsx
+++ b/quartz/util/resources.tsx
@@ -47,7 +47,7 @@ export function JSResourceToScriptElement(resource: JSResource, preserve?: boole
 export function CSSResourceToStyleElement(resource: CSSResource, preserve?: boolean): JSX.Element {
   const spaPreserve = preserve ?? resource.spaPreserve
   if (resource.inline ?? false) {
-    return <style>{resource.content}</style>
+    return <style dangerouslySetInnerHTML={{ __html: resource.content }} />
   } else {
     return (
       <link