v2.47.4

2.47.4 (2026-10-12)

Bug Fixes

• a click is counted from its event's own time, where detail was measured with Date.now() when the handler ran, so a slow render after the first click of a pair lost the double click (#936) (#945) (da1b105)
• a ContextMenu opens with the items of the render the right-click caused, where it decided to open and sized itself from the previous render's, so a first right-click on a Table row whose menu was empty until then opened nothing (#934) (#947) (f7b362f)
• a Dialog is as tall as its content, centred over its owner at that size and capped at the monitor, with the body scrolling and the actions row pinned, where it was 170 pixels whatever it held and the content past that, the actions row first, was cut off at the bottom edge (#940) (#949) (f85473d)
• cocoa: a tray's menu reaches AppKit only when its items change, so a title that ticks every second leaves the NSMenu alone, where every useTray update rebuilt it and the mount sent it twice (#939) (#950) (b59140e)
• cocoa: useClipboard() reads the whole pasteboard — targets() lists its types, org.nspasteboard.ConcealedType included, read() returns an image or Finder's files, and watch() fires on each change by polling the change count while watched, where the shim was text-only and watch() never fired, so the edit menu's Paste row never followed the pasteboard (#937) (#952) (aa44a79)
• cocoa: useIdle reports an empty desk on macOS, from the bridge's lastInputMs where it has one and ioreg's HIDIdleTime where it does not, where no rung reached the system idle time and the hook stayed false (#938) (#951) (6e23927)
• Ctrl, Alt and Super+Return reach the app's shortcuts, where a focused <textinput> submitted on them and a focusable onClick box activated on them, so a modified-Return menu shortcut never fired while either had focus (#935) (#946) (72b6f96)
• types: TabItem.content accepts a function, as the runtime and docs do, where the type allowed only a ReactNode and a lazy tab failed to typecheck (#941) (#948) (fc1d62b)