From 2f85ec5806f519098fbd9f0c9fd572bac7d5c5de Mon Sep 17 00:00:00 2001 From: Jake Date: Thu, 7 May 2026 09:01:41 +0100 Subject: [PATCH] fix(settings): rename text-error/border-error to text-danger so error states actually render The Tailwind v4 @theme block defines --color-danger as the semantic error token, and 15+ files across the codebase use text-danger consistently. SettingsPage was the lone outlier with five text-error / border-error sites (audio devices, profile delete, vocabulary, term delete, diagnostic report). Without a --color-error token, those utilities resolved to the default text colour, so error messages rendered in warm cream instead of red. Verified live via Playwright probe before and after. --- src/lib/pages/SettingsPage.svelte | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/lib/pages/SettingsPage.svelte b/src/lib/pages/SettingsPage.svelte index ac175b9..b7ca500 100644 --- a/src/lib/pages/SettingsPage.svelte +++ b/src/lib/pages/SettingsPage.svelte @@ -1009,7 +1009,7 @@ >Refresh {#if audioDevicesError} -

{audioDevicesError}

+

{audioDevicesError}

{:else if visibleAudioDevices.length === 0}

No input devices detected. Check that a microphone is connected and PulseAudio/PipeWire is running.

{:else} @@ -1061,7 +1061,7 @@ @@ -2241,7 +2241,7 @@ {/if} {#if diagnosticReportError} -

{diagnosticReportError}

+

{diagnosticReportError}

{/if} {#if diagnosticReportSavedTo}

{diagnosticReportSavedTo}