Skip to content

v0.5.83

Choose a tag to compare

@jaspertey jaspertey released this 30 Oct 02:37
52255a2

Upgrading

  • Run kit:update plan|apply for core (re-pinned sha256:230cf6d7…4141 → sha256:446ce6c9…da56): Kit/Form/InputCheckbox.vue, Kit/Form/Select.vue, Kit/Form/FileInput.vue, Kit/Form/RadioCardGroup.vue, Kit/Form/InputRichText.vue, Kit/Form/InputSelect.vue, Kit/Form/InputNumber.vue and Kit/contract.ts take the attribute fix below. InputCheckbox's row is now wrapped in a grid (for its description), so a host that styled its row by structure should check it.

Fixed

  • Kit form controls put your attributes on the control itself, not a wrapper. aria-describedby, aria-invalid, required, aria-label and data-* passed to InputCheckbox landed on its wrapper <div>; on Select they went nowhere (Reka's SelectRoot renders no element); FileInput dropped them; RadioCardGroup and InputNumber replaced or ignored your aria-describedby; InputRichText put them on its frame; and InputSelect dropped a passed required. Each now forwards them to its focusable control (the checkbox button, the select trigger, the file input, the radiogroup, the editable textbox, the combobox input), joins your aria-describedby with its own ids, de-duplicated, and sets aria-required where a native required doesn't apply. class and a style's custom properties stay on the wrapper. InputCheckbox, FileInput, RadioCardGroup and InputRichText take invalid (aria-invalid), and InputCheckbox takes description, shown under the label as <id>-description and joined to its aria-describedby.

What's Changed

  • Forward caller attributes to the focusable control in kit form controls (0.5.x) by @jaspertey in #414

Full Changelog: v0.5.82...v0.5.83