v0.189.0

Minor Changes

• #1432 6f038456 Thanks @solarrust! - Result gains what a confirmation or result dialog needs: an actions slot for Result.Action buttons, which take their size from the Result, a size="large" scale with a bigger icon and text, and a layout="stacked" arrangement that fills the container and stacks the actions to the full width. Size and layout are independent, so a large result can keep its centered row of actions and a medium one can stack them. isCompact keeps its own scale and arrangement and ignores both. The status icon now has 3x of room on every side (a quarter of --icon-size once that is larger, above a 12x icon) in every non-compact Result including the default medium one, a custom icon gets the same room (sized by the Result's --icon-size, so size a custom icon through it rather than on the icon), and that room is the whole distance to the title, so the title keeps its 3x from the icon in both sizes. Outside isCompact the content and the actions now keep their 3x with a top margin instead of the container gap, so a gap passed to such a Result adds to it. A status without an icon (404, 403, 500) renders no icon slot. The stacked layout keeps a 1.5x padding of its own, and none inside a Dialog, whose Content already pads it.

Patch Changes

• #1463 d1215d22 Thanks @tenphi! - Fix three bugs in useAlertDialogAPI().open(). A cancelToken aborted before or while the dialog is open now rejects the promise with undefined, as Cancel does, instead of leaving it pending forever; a caller that aborts without handling that rejection now gets an unhandled rejection where its await used to hang. The default Ok button, shown when actions.confirm is omitted, now resolves 'confirm' instead of rejecting like a dismissal. And a dialog opened while the previous one is still animating out now replaces it instead of being rejected as "Another dialog is already opened", so follow-up dialogs and dialogs opened from a mount effect under StrictMode show. The AlertDialogApi, AlertDialogApiParams and AlertDialogResolveStatus types are now exported, and the AlertDialog docs describe the imperative API.

• #1461 12a62900 Thanks @tenphi! - Update @tenphi/tasty to 3.9.6. It fixes a crash when flow or gap meets an unset display branch (including a null default in a state map), accepts chain in the overscroll-behavior longhands, and lets a transition entry that names one property keep its own timing when a group such as theme that covers it comes later. That gives a board widget's outside resize grip its intended 120 ms ease-in-out fade instead of theme's default timing. Board widget chrome and Popover transitions now also read the kit's duration tokens instead of hardcoded values, with the same timing.

• #1461 12a62900 Thanks @tenphi! - Style overrides that a component layers over its own defaults now merge the way tasty's styles prop does, instead of replacing whole keys. This covers styles on Disclosure (and its group's contentStyles), ButtonSplit, DataTable, ItemTable, Placeholder, Paragraph, Avatar, ActiveZone and DateInput, plus wrapperStyles on the date pickers, inputStyles on PeriodPicker, styles and headerStyles on CommandMenu, popoverStyles on Picker and FilterPicker, overlayStyles on CommandTextArea, closeButtonStyles on Tag, thumbStyles and trackStyles on HueSlider, and triggerStyles, optionStyles and headingStyles on Select. A state map without a '' key now adds states to the default map instead of discarding it, and a sub-element override keeps the default's other properties. A null still resets the component's own value, as before. Renders without such an override are unchanged.