Mixins / foldkit-mixins-ui
ToolbarSlots
const · packages/mixins-ui/src/toolbar.ts:26
const ToolbarSlots: Slots.Contract<{
readonly root: Slot.UnnamedSlot<
Capability.Capability<
'Container',
readonly [
Capability.Capability<
'Interactive',
readonly [Capability.Capability<'Base', readonly []>]
>,
]
>,
readonly [Event.EventToken<'keydown'>],
readonly [
Attr.AttrToken<'role'>,
Attr.AttrToken<'aria-label'>,
Attr.AttrToken<'aria-disabled'>,
],
readonly Slot.RequirementName[],
boolean
>
readonly group: Slot.UnnamedSlot<
Capability.Capability<
'Container',
readonly [
Capability.Capability<
'Interactive',
readonly [Capability.Capability<'Base', readonly []>]
>,
]
>,
readonly Slot.EventName[],
readonly [Attr.AttrToken<'role'>, Attr.AttrToken<'aria-label'>],
readonly Slot.RequirementName[],
boolean
>
readonly separator: Slot.UnnamedSlot<
Capability.Capability<
'Container',
readonly [
Capability.Capability<
'Interactive',
readonly [Capability.Capability<'Base', readonly []>]
>,
]
>,
readonly Slot.EventName[],
readonly [Attr.AttrToken<'role'>],
readonly Slot.RequirementName[],
boolean
>
}>A toolbar publishes its root, the groups that gather related controls
under a name, and the separator between sets. The controls are the
caller's own elements (a Button, a toggle, a menu's trigger), which the
toolbar hands the attributes of its one tab stop; it adds no markup around
them, so a control keeps the class of its own recipe.