Forums Bug Reports Thread

Active Sessions current-row highlight uses hardcoded rgba(44,124,255,...) instead of a semantic token

Patrick Bass · Jun 6 · 16 · 1 Locked
[Cosmetic] [Low Priority] [Bug Fixed] [Always Reproduces]
🚀 OP Jun 6, 2026 5:11pm

Area: Account & identity (audit phase 1) · Surface: /account/sessions (AccountController@activeSessions) · Dimension: law-3-contrast · Severity: cosmetic

The 'this device' row tint is hardcoded to the brand blue's RGB. It happens to read acceptably in both themes at 6% alpha, but it bypasses the theming primitive, so a brand-color change would not propagate and it violates the semantic-token rule.

Evidence

platform/templates/account/sessions.php L60: <tr<?= $isCurrent ? ' style="background:rgba(44,124,255,0.06);"' : '' ?>> — 44,124,255 is the brand blue (#2C7CFF) hardcoded as RGB rather than using a token. Elsewhere in the same area the established pattern is color-mix(in srgb, var(--color-primary) N%, transparent) (e.g. partials/notifications.php:105, profile/show.php:121).

Suggested fix. Replace with background:color-mix(in srgb, var(--color-primary) 6%, transparent); on platform/templates/account/sessions.php:60.

Filed by the automated tenant-app audit (phase 1) and adversarially evidence-verified. Status: verified. Open — not yet actioned.


Patrick Bass
@mobieus

🚀 Jun 7, 2026 5:31am

Resolved — fixed and deployed. Commit af2b6678f082, shipped dev-first then to all tenants on 2026-06-06.

Replaced the hardcoded background:rgba(44,124,255,0.06) inline style on the current-session row (line 60) with background:color-mix(in srgb, var(--color-primary) 6%, transparent), so the highlight uses the semantic primary token and themes correctly in both light and dark.

Status: fixed. Thread closed and locked.


Patrick Bass
@mobieus

Log in or register to reply to this thread.