@webority/theme 0.6.2 → 0.6.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webority/theme",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Webority shared design system — Bootstrap 5.3 SCSS overrides, --wui-* tokens, and shared component CSS. The single source of brand chrome for React portals and Razor sites.",
   "license": "SEE LICENSE IN LICENSE",
   "publishConfig": {

package/scss/_components.scss

@@ -75,6 +75,13 @@
     min-height: var(--wui-control-height);
 }
 
+// Tactile press feedback — every variant AND every size (sm/md/lg). Kept
+// separate from the height rule above so sm/lg (which opt out of the shared
+// control height) still get the nudge. A signal, not a depth cue.
+.btn:not(.btn-pill):not(.btn-pill-sm):not(.u-action):not(.btn-icon):active:not(:disabled) {
+    transform: translateY(1px);
+}
+
 .btn-primary {
     // Pin hover/active to the pressed-primary token so a rebrand tracks
     // automatically instead of Bootstrap auto-shading $primary off-spec.
@@ -82,9 +89,27 @@
     --bs-btn-hover-border-color:  var(--wui-primary-pressed);
     --bs-btn-active-bg:           var(--wui-primary-pressed);
     --bs-btn-active-border-color: var(--wui-primary-pressed);
-    &:active:not(:disabled) {
-        transform: translateY(1px);
-    }
+}
+
+.btn-danger {
+    // Pin hover/active to the pressed-danger token so Bootstrap cannot auto-shade the fill
+    // off-spec — the same treatment .btn-primary gets above. That is what stops the label
+    // flipping between states: once the fill stops moving, color-contrast() resolves the
+    // same way on every state.
+    //
+    // The label is deliberately NOT pinned to white. --wui-danger (#F8285A) carries white
+    // at 3.86:1 and --wui-danger-active (#E82646) at 4.38:1, both under the 4.5:1 AA floor,
+    // so forcing white is a serious color-contrast violation — axe flags it on BOTH
+    // surfaces. Bootstrap's automatic choice (the dark label, 5.44:1) is the accessible one
+    // and is what has always shipped.
+    //
+    // If white-on-red is wanted — it is the conventional destructive look — the fix is to
+    // darken --wui-danger to about #C81340 (white 5.80:1), which is a brand decision, not a
+    // per-component override.
+    --bs-btn-hover-bg:            var(--wui-danger-active);
+    --bs-btn-hover-border-color:  var(--wui-danger-active);
+    --bs-btn-active-bg:           var(--wui-danger-active);
+    --bs-btn-active-border-color: var(--wui-danger-active);
 }