-
Notifications
You must be signed in to change notification settings - Fork 251
[BUG] Bright and Dark mode toggle is non-functional #2061
Copy link
Copy link
Closed
Labels
area:frontendFrontend React/UI workFrontend React/UI workgood first issueFriendly starter issue for first-time contributorsFriendly starter issue for first-time contributorslevel:beginner20 pts difficulty label for small beginner-friendly PRs20 pts difficulty label for small beginner-friendly PRspriority:mediumImportant issue with normal urgencyImportant issue with normal urgencytype:bugBug fix work category bonus labelBug fix work category bonus label
Description
Metadata
Metadata
Assignees
Labels
area:frontendFrontend React/UI workFrontend React/UI workgood first issueFriendly starter issue for first-time contributorsFriendly starter issue for first-time contributorslevel:beginner20 pts difficulty label for small beginner-friendly PRs20 pts difficulty label for small beginner-friendly PRspriority:mediumImportant issue with normal urgencyImportant issue with normal urgencytype:bugBug fix work category bonus labelBug fix work category bonus label
Summary
The light/dark mode theme toggle on the SecuScan web application is currently non-functional. Clicking the theme toggle button does not switch the visual theme between bright and dark modes, leaving the app locked in its default visual state.
Why this matters
Users who prefer dark mode for reduced eye strain or light mode for improved contrast are unable to switch visual preferences. This degrades overall user experience and accessibility across different environments and device settings.
Reproduction steps
List the exact steps needed to reproduce the behavior:
Expected behavior
Clicking the theme toggle should dynamically update the UI theme by toggling theme
Actual behavior
The visual theme remains unchanged regardless of how many times the toggle is clicked. No state transition or root element class update occurs.
Evidence
Environment
Please complete the following information:
Definition of done
Use this section if you already know what a complete fix should include:
Additional context
I would like to work on this issue under GSSoC '26. Please assign this issue to me!