@muten/shadcn 0.2.15 → 0.2.17

package/kit.css

@@ -5639,3 +5639,13 @@ a.cx-bc-item:hover { color: var(--foreground); }
 .cx-sidebar[data-collapsed="true"] .cx-sb-fold > .cx-sb-fold-in { visibility: visible; }
 .cx-sidebar[data-collapsed="true"] :is(.cx-sb-rowtoggle, .cx-sb-chev) { display: none; }
 @media (prefers-reduced-motion: reduce) { .cx-sb-fold, .cx-sb-chev { transition: none; } }
+
+/* ═════ EVERYTHING YOU CAN CLICK SHOWS THE HAND ═════ */
+/* A browser gives a <button> the arrow, and shadcn gives menu items, options and selects `cursor: default` (the desktop-app
+   convention). On the web the hand is what says «this does something», so every enabled control takes it: buttons,
+   tabs, menu items, options, switches, checkboxes, toggles, triggers, labels of a box. Disabled ones keep the arrow, and a
+   modal's backdrop (a button that fills the screen) too. The :is() weighs as an element plus an attribute, so it wins
+   over the single-class `cursor: default` rules above. */
+:is(button, a[href], summary, select, label[for], input[type="checkbox"], input[type="radio"], input[type="range"], input[type="color"], input[type="file"],
+  [role="button"], [role="tab"], [role="menuitem"], [role="menuitemradio"], [role="menuitemcheckbox"], [role="option"], [role="switch"], [role="checkbox"], [role="radio"], [data-slot$="trigger"]):not(:disabled, [aria-disabled="true"], [data-disabled], .cx-overlay) { cursor: pointer; }
+:is(button, [role="button"], [role="menuitem"], [role="option"], [role="switch"], [role="tab"]):is(:disabled, [aria-disabled="true"], [data-disabled]) { cursor: not-allowed; }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@muten/shadcn",
-  "version": "0.2.15",
+  "version": "0.2.17",
   "description": "shadcn-style component registry for muten - own-the-source parts you add with `muten add`.",
   "repository": {
     "type": "git",

package/registry/modal-behavior.js

@@ -5,12 +5,17 @@
 // MODALS STACK (a receipt opened over a cita): Back, Esc and the focus trap belong to the TOP one only, and the page's
 // scroll is unlocked when the last one closes. Each modal used to listen to every Back: closing the receipt went back
 // in history and that Back also closed the cita under it, leaving the agenda without its buttons (21-10-2026).
-const stack = (globalThis.__cxModals ||= { list: [], skip: 0, wired: false });
+// ONE CLOSES AS THE NEXT OPENS («Añadir» → the link's editor): the closing one's history.back() lands after the new one's
+// pushState, and Chrome counts that Back from where it was asked, so it stepped over the new entry. The new modal then
+// closed with a Back that was not its own and took the page one screen back (/shop/import, 31-10-2026). So a modal that
+// opens while a closing Back is still on its way pushes its entry once that Back has landed (`after`).
+const stack = (globalThis.__cxModals ||= { list: [], skip: 0, after: [], wired: false });
+stack.after ||= [];
 if (!stack.wired) {
   stack.wired = true;
   addEventListener('popstate', () => {
     // the history.back() a modal makes when it closes itself is its own, not a Back for the one under it
-    if (stack.skip > 0) { stack.skip -= 1; return; }
+    if (stack.skip > 0) { stack.skip -= 1; if (stack.skip === 0) stack.after.splice(0).forEach((push) => push()); return; }
     stack.list.at(-1)?.onPop();
   });
 }
@@ -59,7 +64,8 @@ export function mount(el, inputs, on) {
     document.documentElement.classList.add('cx-locked');
     // on the phone, focusing a field would throw the keyboard over the sheet: focus the sheet itself
     requestAnimationFrame(() => { ((mdl.dataset.mode === 'dialog' && focusables().find((x) => x.matches('input, textarea'))) || mdl).focus({ preventScroll: true }); });
-    history.pushState({ cxModal: 1 }, ''); pushed = true;
+    const push = () => { if (!isOpen || pushed) return; history.pushState({ cxModal: 1 }, ''); pushed = true; };
+    if (stack.skip > 0) stack.after.push(push); else push();
   };
   const shut = () => {
     if (!isOpen) return; isOpen = false;