website: warn when JS is disabled that the console won't open - #32
Merged
Merged
Conversation
Adds a <noscript> banner above the nav, styled to match the site (dark theme, amber warning accent). It lives in index.html outside the React tree entirely, so it's immune to the React+noscript hydration bug where reconciliation ends up rendering noscript children even with JS enabled. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
4 tasks
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<noscript>banner above the nav that tells visitors with JS disabled the live console demo won't open (the rest of the page still works, per the prerendering in website: prerender to static HTML for no-JS crawlers/agents #31).max-w-6xlcontent width as the nav.index.html, outside the React tree, on purpose — a<noscript>wrapping JSX children in a hydrated React app is unreliable (React's hydration reconciliation ends up creating the children as real DOM nodes even with JS enabled, since React doesn't respect the HTML parser's noscript-content-as-text behavior). Keeping it as plain HTML sidesteps that entirely: React never touches it, and the browser's native noscript handling does the hiding.Test plan
bg-amber-400,border-amber-400,text-amber-200) made it into the compiled CSS — confirms Tailwind's content scan coversindex.html.pnpm run typecheckandpnpm run lint(oxlint, repo-wide) pass with no new warnings.🤖 Generated with Claude Code