v0.190.1

Patch Changes

• #1470 e7bf7d2e Thanks @tenphi! - A disabled or loading Button that has a tooltip, or renders as a link, no longer opens its MenuTrigger menu from the keyboard (Enter, Space or ArrowDown), as ItemButton and ItemAction already did not. Enter or Space on such a Button, ItemButton or ItemAction also no longer clicks the element around it, so a clickable row or card doesn't react.

• #1467 05f03e86 Thanks @tenphi! - A press on a popup that is closing no longer closes the Dialog underneath and loses what was typed in it. A list closes on its own when the content around its trigger scrolls, so a trackpad's momentum was enough for a click on a still-visible option to dismiss the whole Dialog; a second click on a nested Dialog that was already closing did the same. The press now reaches the popup instead, so the option clicked in a fading list is picked, and an Escape pressed while a nested modal or tray is still closing reaches the Dialog under it instead of being lost. This covers Select, ComboBox, Picker, FilterPicker, menus and every other popover, modal and tray. Pressing an action on a toast or notification while a Dialog is open now runs it too, instead of closing the Dialog and dropping the press. DisplayTransition's render prop also receives isExiting: true from the render where the isShown prop turns false until the exit finishes.

• #1470 e7bf7d2e Thanks @tenphi! - A control that keeps keyboard focus while disabled now shows its focus ring: a disabled Button or ItemAction that has a tooltip or renders as a link, a disabled ItemButton of a type with a ring (outline, primary, clear), and a disabled interactive InfoBadge. The default item type has no ring, since its rows show focus with their fill, so a disabled one shows no focus, as before. A disabled current primary chip no longer darkens when focused. Before, the ring disappeared while the control was disabled and stayed gone after it was enabled, until focus left and came back. A control also drops a focus ring it lost without a blur, as when its tooltip is added or removed while it is focused and the element is replaced, or a fieldset around it is disabled: right away when the control re-renders, otherwise on the next key or pointer press, so a Tab no longer leaves two rings.

• #1468 04d2e872 Thanks @tenphi! - Keep selected button and item fills identical when disabled by removing obsolete alpha adjustments for Tasty's fixed state-priority issue. Disabled labels remain muted, and hover, focus and pressed states retain their intended priority.

• #1470 e7bf7d2e Thanks @tenphi! - ItemAction (Item.Action) now disables itself while isLoading, as Button does, so a second press while loading no longer runs the action again. Loading always wins: isDisabled={false} still overrides a disabled row, but not a loading action. A loading action is marked aria-disabled rather than natively disabled, so it keeps keyboard focus and its tooltip, while Tab skips it until loading ends. An icon-only action with a tooltip that disables itself is marked the same way, so keyboard users can still reach it and read the tooltip, as on Button. Inside a disabled row, a disabled button action that is not loading stays natively disabled, and no disabled action fades twice. The loading spinner on a label-only action now gets the same padding as an icon. An interactive InfoBadge follows the same rules.