docs: describe the component kit on its own terms

The kit's comments and docs describe its props and classes directly instead
of by reference to another kit.
This commit is contained in:
Sameh Khamis committed 2026-11-01 19:40:46 -08:00
1 parent 859ceac8b4
commit 5582ff288d
12 files changed
+33 -46

No files matched your search

+3 -4
View File
@@ -1,11 +1,10 @@
<script setup>
import { computed } from 'vue';
// Core's segmented control, with @halfpixel/ui-vue UiSegmented's
// v-model, options, label, stacked and disabled so the two kits can merge.
// Core adds `keyboard`, because its groups keep their own policy: `none`
// Core's segmented control, with v-model, options, label, stacked and
// disabled. It adds `keyboard`, because its groups keep their own policy: `none`
// (Tab reaches every option and arrows do nothing), `arrows` (a roving tab
// stop that arrows move, as in ui-vue) or `radio` (arrows plus Home and
// stop that arrows move) or `radio` (arrows plus Home and
// End). Each option may carry `attrs` (an id, data attributes, a tip), and
// Core's classes sit beside the kit's: `gev-segmented`, `gev-segment` and the
// selected option's `activeClass`. Not mirrored yet: an option's icon.