The contact-effect editor's accent is the org's primary, not a fixed purple

Fixkamo-internal
Shipped
September 7, 2026 at 7:42 PM UTC
Author
Kamo
Commit
8158ae5

The editor painted its reset control and its "Following the shipped default" helper lines in #8b5cf6, hardcoded four times over — the shared editor's default plus one ACCENT constant at each of the three panes. The effects those lines describe have never been purple: resolvePalette in paint.ts reads --color-primary and mixes the whole palette from it, so the text explaining an effect was in a colour that effect never used, on every tenant whose brand is not violet. All four become var(--color-primary). The two the editor itself uses are text colours; the organization's section on Behavior & Labeling also builds a border, a hover wash and a badge out of the same constant via color-mix, which resolves over a variable the same way — the editor already relies on that for its own row hairlines. Verified in a browser at two brands: the reset control and the inherit helper compute to rgb(37, 99, 235) under #2563eb and rgb(15, 118, 110) under #0f766e, following the variable rather than merely being non-purple. The reset control has to be ENABLED to see it — a disabled MUI button paints its own grey over the sx colour and the accent never shows.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing