@danxbot/ui 3.9.0 → 3.9.1

package/dist/index.js

@@ -6812,6 +6812,33 @@ const uw = vt({
        The size never moves either: the label stays in the layout at opacity 0
        with the spinner absolutely positioned over it. */
     "disabled:not-data-loading:opacity-45",
+    /* THE SOFT FORM OF OFF HAS TO DIM TOO, and until now only the native one
+           did. `aria-disabled` is this library's stance for a control that must
+           stay hoverable so it can explain itself (`IconButton.disabledReason`) —
+           and it is ALSO what a control becomes when it is not asking to: Base UI
+           deletes the native `disabled` attribute off a composite item that renders
+           another button (`useButton`: "the `disabled` prop needs to pass through 2
+           `useButton`s then finally delete the `disabled` attribute from DOM").
+    
+           MEASURED, because the form matters and the obvious reading of it is
+           wrong. `<ToolbarButton render={<Button disabled/>}/>` — disabled on the
+           INNER button — keeps `disabled=true` and dims as it always did. It is
+           `disabled` on the TOOLBAR ITEM that gets deleted: both
+           `<ToolbarButton disabled render={<Button/>}/>` and a plain
+           `<ToolbarButton disabled>` come out `disabled=false`,
+           `aria-disabled="true"`, `data-disabled=""` — full opacity, pointer
+           cursor, no-op click. A control that looks armed and does nothing is the
+           worst of the three states, and it was reported by a consumer who kept a
+           hand-rolled action bar rather than accept it.
+    
+           So the look is keyed to BOTH forms. Not `pointer-events-none` though:
+           that is exactly what makes a natively-disabled control unhoverable and
+           its tooltip unreachable, and reaching it is the entire reason the soft
+           form exists. The click is already inert — `Button` treats `aria-disabled`
+           as disabled for the ripple, Base UI no-ops the handler — so what was
+           missing was only the two lines that SAY so. */
+    "aria-disabled:not-data-loading:opacity-45",
+    "aria-disabled:cursor-not-allowed aria-disabled:active:translate-y-0",
     "data-loading:pointer-events-none data-loading:cursor-wait"
   ],
   variants: {
@@ -28844,6 +28871,7 @@ function n_({
           {
             type: "button",
             onClick: d ? void 0 : () => n(u.value),
+            "aria-label": u.label,
             "aria-disabled": d || void 0,
             "aria-describedby": d ? p : void 0,
             className: j(
@@ -30807,8 +30835,8 @@ function i6({ className: e }) {
   );
 }
 function a6({
-  variant: e = "ghost",
-  size: t = "sm",
+  variant: e,
+  size: t,
   iconOnly: n,
   className: r,
   children: o,
@@ -30819,7 +30847,10 @@ function a6({
     JS,
     {
       ref: s,
-      className: j(uw({ variant: e, size: t, iconOnly: n }), r),
+      className: i.render === void 0 ? j(
+        uw({ variant: e ?? "ghost", size: t ?? "sm", iconOnly: n }),
+        r
+      ) : r,
       ...i,
       children: o
     }
@@ -47222,6 +47253,7 @@ export {
   Yy as AmbiguousTimeError,
   _H as AppShell,
   LE as Attachment,
+  By as AttachmentAction,
   zE as AttachmentList,
   u3 as AttachmentPreview,
   tc as Avatar,