Skip to content

Commit 4e7a6df

Browse files
committed
fix(theme): stop inverting the home branding in dark mode
The previous commit made the home logo's fill theme-driven (`currentColor` + `text-primary`) but left the pre-existing `dark:invert` in place. A CSS filter does not care where the colour came from, so in dark mode a deployer's configured primary is painted as its complement - with `primary: '#2dd4bf'` the logo renders red - which defeats the customisation this PR documents. Thanks @chatgpt-codex-connector for catching it. The adjacent `<h1>` is included even though this PR did not introduce it: the two are siblings in the same hero lockup and carry the same `text-primary dark:invert`, so removing the inversion from only the logo would leave the mark and the wordmark in complementary colours next to each other. Verified with the reviewer's example value: both now compute rgb(43, 212, 189) with `filter: none`, matching the configured #2dd4bf, where before the filter painted them rgb(212, 43, 66). Note this leaves ~30 other `text-primary dark:invert` pairs elsewhere in the codebase untouched. They predate this PR and have the same conflict with a customised theme, but they are outside the branding this change concerns.
1 parent 80fc1f2 commit 4e7a6df

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

src/pages/index.vue

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ const chainStore = useBlockchain();
4949
<g
5050
transform="translate(0.000000,132.000000) scale(0.100000,-0.100000)"
5151
:fill="chainStore.current?.themeColor || 'currentColor'"
52-
class="text-primary dark:invert"
52+
class="text-primary"
5353
stroke="none"
5454
>
5555
<path
@@ -75,7 +75,7 @@ const chainStore = useBlockchain();
7575
</g>
7676
</svg>
7777
</div>
78-
<h1 class="text-primary dark:invert text-3xl md:!text-6xl font-bold">
78+
<h1 class="text-primary text-3xl md:!text-6xl font-bold">
7979
{{ $t('pages.title') }}
8080
</h1>
8181
</div>

0 commit comments

Comments
 (0)