parseUserAgent in ProfilePage.jsx has weak OS detection #56
Labels
No Label
architecture
backend
bug
feature
frontend
priority:critical
priority:high
priority:low
priority:medium
priority:nice-to-have
ux
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/BillTracker#56
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity: LOW 🔵
Affected Files
client/pages/ProfilePage.jsx—parseUserAgent()Problem
The OS extraction in
parseUserAgent()only checks a handful of UA strings. Modern Linux desktops, ChromeOS, and some Android OEM user agents would fall through tonullOS and no icon. The login history modal would show an empty OS field for these users.Current detection patterns (approximate):
WinMacAndroidiPhone/iPadLinuxMissing: ChromeOS, Fedora/Ubuntu/Debian distro strings, some Android OEM UAs.
Impact
Fix
Add fallback patterns for ChromeOS (
CrOS) and common Linux distros. If OS is null after all checks, fallback to a generic "Unknown" label rather than showing nothing.Acceptance Criteria