Nonce Consumers

Every component that consumes your CSP nonce - and what silently dies without it.

Why This Table Exists

Every component below renders an inline <script> (or a nonce-gated attribute set) and takes the consumer's CSP nonce through its props. A call site that passes an empty nonce renders markup that silently dies under a nonce-locked CSP: browsers reject nonce="", the script never executes, and the component looks fine in string tests. This is the bug class behind the 2026-10-12 fleet audit (cqrs-htmx CopyButton ×13, GmbH ThemeToggle, KeyHolderAI ToastContainer — three repos, one root cause: "component renders a script, consumer didn't know").

Run tc doctor in your repo: it scans your .templ sources for nonce-less call sites to the components in this table and fails when your repo declares a Content-Security-Policy (informational otherwise). The canonical table lives in the repository at docs/nonce-consumers.md, pinned to the doctor's scan list by cmd/tc.TestNonceConsumerDocsSync and to the integration nonce render tables by cmd/tc.TestNonceConsumerIntegrationSync.

The library's own guarantee (omit-empty rule, issues #7/#9/#24): an empty Nonce OMITS the attribute entirely — the library never renders a broken nonce="". The failure mode is consumer-side: you hold a per-request nonce and forget to thread it. See CSP Compliance for the threading patterns.

The Table

navigation.MobileMenu's toggle script also consumes a nonce; consumers reach it through navigation.Nav/SimpleNav — pass the nonce to the nav component (the constructor is positional-arg based, so it is documented here rather than in the scan table).