v0.1.0-alpha.16

One new Tooltip prop. Nothing renders differently unless you pass it.

Added

toggleable makes the trigger a control (#29). With it, the trigger carries role="button" and an aria-expanded that tracks the content, and Enter and Space toggle it. Both keys are prevented from their defaults, since Space scrolls the page and Enter submits an enclosing form.

It is opt-in because a trigger whose content only supplements what is already on screen is not a control and should not announce itself as one. A glossary term is the opposite case: the definition is something a reader summons deliberately, and where there is no hover at all, activation is the only route to it.

Both continuum-hub and backend.ai-go have a glossary Term, both written before this package existed, and both built the same trigger contract around it: tabIndex={0}, role="button", aria-describedby, aria-expanded bound to the open state, Enter and Space toggling, Escape closing. The first of them lost that contract when it moved onto this component, which is what this prop is for.

Before you upgrade

A minor addition. toggleable defaults to false, and with it off the component behaves exactly as 0.1.0-alpha.15 did.

Full changelog: v0.1.0-alpha.15...v0.1.0-alpha.16