v0.137.1

Patch Changes

• #1160 17d67406 Thanks @tenphi! - InlineInput: improved keyboard accessibility and stability.

  • New prop keyboardActivation?: boolean (default true). When enabled, the display element is keyboard-focusable (tabIndex=0, role="button", aria-roledescription="editable text") and responds to Enter, F2, and Space to enter edit mode. Hosts that already own keyboard activation (e.g. editable tabs whose <button> listens for F2) can pass keyboardActivation={false} to avoid creating a nested tab stop.
  • A keyboard focus ring (#primary token, rounded) appears on the display element when it receives keyboard focus (useFocusRing's isFocusVisible). It is suppressed automatically while editing (focus is on the inner input) and when keyboardActivation={false} (so the host's focus ring is the one users see — as in Tabs). New focused modifier exposed on the root for consumers.
  • The display element now mirrors isDisabled / isReadOnly via aria-disabled / aria-readonly, and aria-label / aria-labelledby are forwarded to it when focusable.
  • Pointer activators (onClick / onDoubleClick) are now wired only when the chosen editTrigger actually needs them, instead of being always-on no-ops.
  • Internal fixes: stopEditing() reads the synchronous isEditingRef instead of a potentially stale render closure, and the ref mirror is updated via useLayoutEffect so torn-away concurrent renders cannot leak a stale value across commits.

  Tabs: editable tabs continue to be driven by F2 / context-menu rename at the tab-button level; InlineInput now receives keyboardActivation={false} from TabButton so the inline title does not introduce an extra tab stop or a duplicate focus ring inside the tab.

  Layout fix: the InlineInput root is now inline-flex (with align-items: baseline) instead of inline-block, and the truncation moved to a new inner Display sub-element. CSS 2.1 §10.8.1 forces an inline-block with overflow: hidden to use its bottom margin edge as the baseline, which visibly shifted text upward inside surrounding line boxes (most noticeable inside Tabs' centered Item.Label). inline-flex derives its baseline from the first flex item's content baseline, restoring proper alignment with neighbouring text. Truncation, ellipsis, and the overflow auto-tooltip continue to work; only the host responsibility for clipping moves to the inner block, which doesn't perturb the parent baseline.

• #1160 17d67406 Thanks @tenphi! - InlineInput / Tabs: truncate long values with an ellipsis and surface a tooltip with the full value when truncated.

  • InlineInput now renders as display: inline-block with text-overflow: ellipsis / white-space: nowrap / overflow: hidden capped at max-width: 100% in display mode. The truncation rules are relaxed while editing (overflow: visible, white-space: normal) so the auto-sizing input is never visually clipped.
  • New props tooltip?: AutoTooltipValue (default true) and tooltipPlacement?: OverlayProps['placement'] (default 'top'). tooltip={true} shows the full value as a tooltip when the text is truncated; tooltip="..." always shows a custom tooltip; tooltip={false} opts out. The tooltip is automatically suppressed while editing and when renderDisplay is used.
  • Tabs: editable tabs now route <Tab tooltip> through InlineInput (single tooltip owner) — Item's own tooltip is disabled for editable tabs to avoid double-wrapping. Long editable tab titles now also truncate with an ellipsis and reveal the full title on hover/focus, with no extra configuration. Non-editable tabs are unchanged.