Repository navigation
Tell the Dark Reader extension to stand aside (darkreader-lock) - #23
Merged
Merged
Conversation
…heet This page draws its own dark theme; Dark Reader repainted it on top and the hero's brand wash vanished under it (seen on go-fft). The meta lives in the styles.html partial, which every page includes in <head>, so the landing and any other page on the kit carry it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
This page draws its own dark theme (prefers-color-scheme and the System/Light/Dark toggle). The Dark Reader extension repainted it on top: on go-fft the hero's brand wash vanished while the identical CSS showed on go-ndarray.
<meta name="darkreader-lock">asks it to stand down, as go-pdfkit's page and our Hextra fork already did.It goes in the
styles.htmlpartial, which every page includes in<head>, so it travels with the landing kit (logos/landing-kit) to every landing using it. Checked: the built site carries the meta exactly once, inside<head>, on every page that has one.🤖 Generated with Claude Code