Commit827dcf9

chore(layout): keep tag-like literals out of the inlined stylesheet comment

chore(layout): keep tag-like literals out of the inlined stylesheet comment

The comment added in a48f839 explaining the .auth-container heading rule
contained literal "<h1>" and "$1" text. That stylesheet string is emitted
verbatim into every page, so the markup then appeared to contain extra h1
elements and stray "$1" placeholders — which is exactly the confusion the
comment was documenting. Reworded without the literals.

Harmless to rendering (style content is not parsed as markup), but it misleads
anything that greps the HTML, including a person debugging the very issue the
comment describes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

ccantynz-alt committed on July 27, 2026Parent: a48f839

1 file changed+6−6827dcf9b9cea15a0fe3603b708e382ca002e34d3

1 changed file+6−6

Modifiedsrc/views/layout.tsx+6−6View fileUnified Split

@@ -2224,12 +2224,12 @@ const css = `

22242224 position: relative;

22252225 overflow: hidden;

22262226 }

2227 /* h1 and h2 share this rule so the auth pages' primary heading can be a

2228 semantic <h1> — which is what it is — without any visual change. The

2229 register page previously had NO h1 element at all: its only <h1> in the

2230 markup sits inside the inlined client-side markdown renderer's JS

2231 (views/client-js.ts replaces /^# (.+)$/ with '<h1>$1</h1>'), which is

2232 script text, not DOM. */

2227 /* Both heading levels share this rule so an auth page's primary heading can

2228 be semantically top-level without any visual change; the rule fully

2229 specifies size and weight, so narrowing it would let the generic heading

2230 size take over. See src/routes/auth.tsx for why these were h2. NOTE: this

2231 string is emitted verbatim into every page, so keep tag-like literals out

2232 of it — they make the markup look like it contains elements it does not. */

22332233 .auth-container h1,

22342234 .auth-container h2 {

22352235 margin: 0 0 8px;

22362236