/* ========================================================================== HAVN — one hover contract for every button in the app (v2.2.178) CEO directive: get rid of the highlight colour. A button filled with gold hid its own label, and the marketing site's unfenced `.havn-btn` rule filled them with a far brighter #FFC03D, which hid it completely. Nothing in the app is a block of yellow any more. What replaces it, everywhere, is one gesture: hover -> the button lifts 1px and takes a gold edge Four details in here are deliberate and easy to undo by accident: 1. THE LIFT USES `translate`, NOT `transform`. The independent `translate` property composes with whatever `transform` an element already carries; `transform: translateY(-1px)` would REPLACE it. Several buttons are centred with a transform of their own — `.havn-ot-car-arrow` sits at `top:50%; transform:translateY(-50%)` — and writing this as a transform drops them half their height down the page on hover. 2. THE GOLD EDGE IS A RING, NOT A BORDER. Buttons in this app disagree about whether they have a border at all (`.havn-ag-mx-alt` sets `border:0`), so `border-color` alone is invisible on half of them and adding a border changes the layout on the other half. A 1px box-shadow ring paints the same edge on both and moves nothing. `border-color` is set as well, so a button that already has a border turns gold rather than growing a second line just outside it. 3. THE EXCLUSIONS ARE `:not()`, NOT AN UNDO RULE. A later rule setting `border-color: initial` does not restore the button's own border colour — `initial` for border-color is `currentColor`, so it would repaint the border in the text colour. The only way to leave an element's own styling untouched is to never match it, which is what the :not() list does. 4. THE GOLD IS A FIXED PAIR, NOT `--mc-accent`. The shell writes `--mc-accent` inline from the agency's own brand colour, so reading it here would make "gold" mean whatever an agency picked — and v2.2.177 found that inline accent landing at 2:1 in light mode. This is gold because the directive says gold. Loaded last of the plugin's stylesheets (see havn-dashboard.php), so it settles the hover for modules whose own sheets come earlier. The classes the marketing site reaches with `!important` — .havn-btn, .havn-btn-primary, .havn-btn-ghost — cannot be answered from here at all; they are answered in the body-qualified block havn-dashboard.php prints at wp_head priority 99. ========================================================================== */ /* -------------------------------------------------------------------------- Tokens. `html:root` rather than `:root`: the marketing site prints its own `:root` block AFTER every plugin stylesheet, so a plain `:root` here loses on source order — that is exactly how --havn-text got flipped to black on every dashboard page. `html:root` is (0,1,1) against its (0,1,0) and wins whatever the order. -------------------------------------------------------------------------- */ html:root { --havn-hover-line: #D4B370; /* the gold edge */ --havn-hover-glow: rgba(0, 0, 0, .45); /* what sells the lift */ --havn-hover-rise: -1px; /* "slight" is the point */ } /* Light mode: #D4B370 on white is a pale smear, so the edge goes deeper. The toggle mirrors its class onto and , but the shell carries `.havn-mc.is-light` from the first paint, before that JS has run — so the token is declared in both places or the first frame is wrong. */ html.havn-mc-light:root, body.havn-mc-light, .havn-mc.is-light { --havn-hover-line: #A8843C; --havn-hover-glow: rgba(21, 23, 28, .18); } /* -------------------------------------------------------------------------- What counts as a button, and what is exempt. Kept as two long lists rather than a dozen module-specific rules so there is exactly one place to read the contract. Every argument is a simple type, class or attribute selector, so :is() and :not() each contribute (0,1,0) and the whole thing sits at a predictable (0,3,1) — high enough to settle a module's own hover, low enough that a module can still answer it on purpose without reaching for !important. The exemptions are each here for something that shows on screen: .havn-ag-mx-open an invisible