Botón segmentado
Permite elegir una opción, o varias, entre dos y cinco opciones relacionadas que se dibujan una junto a otra como los segmentos unidos de un solo control.
- Categoría
- Acciones
- Tokens
comp.segmented-button- Nivel
- Base
- Web
tanrei-segmented-buttonschedule - SwiftUI
TanreiSegmentedButtonschedule - Jetpack Compose
TanreiSegmentedButtonschedule - Flutter
TanreiSegmentedButtonschedule - React Native
SegmentedButtonschedule
Generado a partir de docs/status/status.json, specs/segmented-button.spec.json
No está en todos los sistemas de diseño
Lo incluyen cupertino, m3-expressive-like, m3-like, registrado por @tanrei/web/cupertino, @tanrei/web/m3-expressive-like, @tanrei/web/m3-like.
No está en tanrei. One choice among several is told by what it changes: tabs where it switches the content below, radio buttons where it sets a value, a button group where each button toggles on its own. Usa Tabs, Radio button, Button group en su lugar.
Un producto sobre un sistema que no lo tiene puede usarlo igualmente: inclúyelo en tu propia capa (Tu propio sistema de diseño) e importa su propio módulo. Entonces se dibuja con los tokens de tu propio sistema.
"components": {
"include": ["segmented-button"]
}import '@tanrei/web/components/segmented-button';Selección única, con iconos y de solo icono
m3-likeUn botón segmentado recibe sus segmentos como cada plataforma recibe los hijos repetidos: elementos hijos en la web, vistas en un view builder en SwiftUI, llamadas en una lambda de contenido en Compose, una lista segments en Flutter y un array items en React Native. La selección pertenece al conjunto, por valor. selection indica si es un valor o varios.
<tanrei-segmented-button label="Intervalo" value="week">
<tanrei-segment value="day" label="Día"></tanrei-segment>
<tanrei-segment value="week" label="Semana"></tanrei-segment>
<tanrei-segment value="month" label="Mes"></tanrei-segment>
</tanrei-segmented-button>
<!-- Varios a la vez. values es una propiedad (un array); el atributo admite un array JSON o valores separados por espacios. -->
<tanrei-segmented-button id="days" selection="multiple" size="small" label="Días" values="mon tue">
<tanrei-segment value="mon" label="Lun"></tanrei-segment>
<tanrei-segment value="tue" label="Mar"></tanrei-segment>
<tanrei-segment value="wed" label="Mié" disabled></tanrei-segment>
</tanrei-segmented-button>
<script type="module">
import '@tanrei/web/components/segmented-button';
// El elemento actualiza su propio value o values y después emite change.
document.querySelector('[label="Intervalo"]').addEventListener('change', (e) => showRange(e.detail.value));
document.querySelector('#days').addEventListener('change', (e) => setDays(e.detail.values));
</script>// El sistema predeterminado deja fuera el botón segmentado: está en las entradas de m3-like, m3-expressive-like y cupertino, y en /all.
import { Segment, SegmentedButton } from '@tanrei/react/m3-like';
// detail es { value } para una sola elección y { values } para varias.
<SegmentedButton label="Intervalo" value={range} onChange={(e) => 'value' in e.detail && setRange(e.detail.value)}>
<Segment value="day" label="Día" />
<Segment value="week" label="Semana" />
<Segment value="month" label="Mes" />
</SegmentedButton>
<SegmentedButton selection="multiple" label="Días" values={days} onChange={(e) => 'values' in e.detail && setDays(e.detail.values)}>
<Segment value="mon" label="Lun" />
<Segment value="tue" label="Mar" />
<Segment value="wed" label="Mié" disabled />
</SegmentedButton>import Tanrei
// El tipo del binding es la selección: un valor opcional para una, un Set para varias.
// Aplica .tag y .labelStyle al propio TanreiSegment, antes que cualquier otro modificador.
TanreiSegmentedButton("Intervalo", selection: $range) {
TanreiSegment("Día").tag("day")
TanreiSegment("Semana").tag("week")
TanreiSegment("Mes").tag("month")
}
// .labelStyle(.iconOnly) equivale a labelHidden: el título sigue dando nombre al segmento.
TanreiSegmentedButton("Alineación del texto", selection: $alignment) {
TanreiSegment("Alinear a la izquierda", icon: "format_align_left").tag("start").labelStyle(.iconOnly)
TanreiSegment("Centrar", icon: "format_align_center").tag("center").labelStyle(.iconOnly)
TanreiSegment("Alinear a la derecha", icon: "format_align_right").tag("end").labelStyle(.iconOnly)
}import io.github.chnotchy.tanrei.components.TanreiSegment
import io.github.chnotchy.tanrei.components.TanreiSegmentedButton
import io.github.chnotchy.tanrei.components.TanreiSegmentedButtonSelectionMode
import io.github.chnotchy.tanrei.primitives.TanreiText
import io.github.chnotchy.tanrei.tokens.TanreiSegmentedButtonSize
// Un solo callback para ambas selecciones. Un conjunto de elección única pasa un conjunto de un elemento.
TanreiSegmentedButton(
onSelectionChange = { range = it.single() },
contentDescription = "Intervalo",
selectedValue = range,
) {
TanreiSegment(value = "day", label = "Día")
TanreiSegment(value = "week", label = "Semana")
TanreiSegment(value = "month", label = "Mes")
}
TanreiSegmentedButton(
onSelectionChange = { days = it },
contentDescription = "Días",
selectionMode = TanreiSegmentedButtonSelectionMode.Multiple,
selectedValues = days,
size = TanreiSegmentedButtonSize.Small,
) {
TanreiSegment(value = "mon", label = "Lun")
TanreiSegment(value = "tue", label = "Mar")
// Compose usa el parámetro inverso.
TanreiSegment(value = "wed", label = "Mié", enabled = false)
}
// labelHidden dibuja solo el icono. La etiqueta sigue dando nombre al segmento.
TanreiSegment(value = "start", label = "Alinear a la izquierda", labelHidden = true, icon = { TanreiText("format_align_left") })import 'package:tanrei/tanrei.dart';
// Con la forma de SegmentedButton: un Set guarda la selección, con un miembro como máximo en la selección única.
TanreiSegmentedButton<String>(
semanticLabel: 'Intervalo',
selected: <String>{range},
onSelectionChanged: (Set<String> value) => setState(() => range = value.single),
segments: const <TanreiSegment<String>>[
TanreiSegment<String>(value: 'day', label: 'Día'),
TanreiSegment<String>(value: 'week', label: 'Semana'),
TanreiSegment<String>(value: 'month', label: 'Mes'),
],
);
TanreiSegmentedButton<String>(
semanticLabel: 'Días',
multiSelectionEnabled: true,
size: TanreiSegmentedButtonSize.small,
selected: days,
onSelectionChanged: (Set<String> value) => setState(() => days = value),
segments: const <TanreiSegment<String>>[
TanreiSegment<String>(value: 'mon', label: 'Lun'),
TanreiSegment<String>(value: 'tue', label: 'Mar'),
TanreiSegment<String>(value: 'wed', label: 'Mié', enabled: false),
],
);
// labelHidden dibuja solo el icono. La etiqueta sigue dando nombre al segmento.
const TanreiSegment<String>(value: 'start', label: 'Alinear a la izquierda', icon: Icon(AppSymbols.formatAlignLeft), labelHidden: true);import { SegmentedButton } from '@tanrei/react-native';
// Controlado: onSelectionChange recibe el valor (single) o los valores (multiple).
<SegmentedButton
accessibilityLabel="Intervalo"
value={range}
onSelectionChange={setRange}
items={[
{ value: 'day', label: 'Día' },
{ value: 'week', label: 'Semana' },
{ value: 'month', label: 'Mes' },
]}
/>
<SegmentedButton
selectionMode="multiple"
accessibilityLabel="Días"
size="small"
values={days}
onSelectionChange={setDays}
items={[
{ value: 'mon', label: 'Lun' },
{ value: 'tue', label: 'Mar' },
{ value: 'wed', label: 'Mié', disabled: true },
]}
/>
// Un segmento de solo icono: { value: 'start', label: 'Alinear a la izquierda', icon: 'format_align_left', labelHidden: true }Tamaños y segmentos deshabilitados
m3-likeAnatomía
Propiedades
| Propiedad | Tipo | Valor predeterminado | Descripción |
|---|---|---|---|
selection | single | multiple | "single" | single lets people choose one option at a time, as a radio group does; multiple lets them switch each option on and off. |
value | string | null | The value of the selected segment while selection is single; null selects none. The segmented button sets it when a segment is activated and emits change; the product may also set it. |
values | strings | | The values of the selected segments while selection is multiple: a list of strings (the platforms take a set). An empty list selects none. |
size | small | medium | large | "medium" | Visual height (32 / 36 / 40), matching Button's heights so that the set can share a row with buttons. The hit area always meets the minimum target. A design system may add values. |
label | string | "" | The accessible name of the set: the question its options answer ("Range", "Text alignment"). Required. |
Eventos
| Evento | Descripción |
|---|---|
change | The user changed the selection; carries value (single) or values (multiple) after the change, which the set now holds. |
Elementos
Los tipos de elemento que el componente repite. Un fixture enumera sus elementos en orden; cada plataforma nombra cada tipo según su propio estilo.
segment
One option of the set: a label, an optional icon, and the value that selects it.
| Propiedad | Tipo | Valor predeterminado | Descripción |
|---|---|---|---|
value | string | "" | Identifies the segment: the set's value or values name it by this, and change carries it. Unique within the set; required. |
label | string | "" | The segment's text and its accessible name. Required, even when labelHidden is true. |
icon | string | "" | The name of an icon (a glyph of the system's icon set). Give every segment of a set an icon, or none. |
labelHidden | boolean | false | Draws the icon alone and keeps label as the accessible name (an icon-only segment). |
disabled | boolean | false | Prevents choosing or clearing the segment; the arrow keys skip it. |
| Especificación | Web | SwiftUI | Jetpack Compose | Flutter | React Native |
|---|---|---|---|---|---|
| Elemento | tanrei-segment | TanreiSegment | TanreiSegment | TanreiSegment | Segment |
value · Propiedad | value | tag | value | value | value |
label · Propiedad | label | title | label | label | label |
icon · Propiedad | icon | icon | icon | icon | icon |
labelHidden · Propiedad | labelHidden | labelStyle | labelHidden | labelHidden | labelHidden |
disabled · Propiedad | disabled | disabled | enabled | enabled | disabled |
| Notas | A child element: <tanrei-segment value="week" label="Week" icon="…">, with label-hidden and disabled attributes, as <option> in a <select>. | TanreiSegment(_ title:, icon:).tag(value) in the view builder, as a Picker's tagged options; .labelStyle(.iconOnly) is labelHidden; disabled follows .disabled(_:). | TanreiSegment(value, label, icon, labelHidden, enabled) called in the TanreiSegmentedButton { } content lambda. enabled is the inverse flag. | TanreiSegment<T>(value:, label:, icon:, labelHidden:, enabled:) in the segments: list. enabled is the inverse flag. | The element type of the set's items array: { value, label, icon?, labelHidden?, disabled? }, where icon is the glyph's name. |
Estados
Comportamiento
Requisitos en formato EARS. Cada implementación de plataforma se prueba contra estos identificadores. El texto de los requisitos se muestra tal como está en la especificación, en inglés.
| ID | Requisito |
|---|---|
SEG-1 | WHEN the user activates an enabled segment by pointer, touch, Enter or Space WHILE selection is single and value is not that segment's value THE segmented button SHALL set value to the segment's value, so that the segment that was selected becomes unselected, and emit change exactly once with it; WHEN the segment is already selected THE segmented button SHALL change nothing and emit nothing, because a single choice is never cleared by its own segment. |
SEG-2 | WHEN the user activates an enabled segment by pointer, touch, Enter or Space WHILE selection is multiple THE segmented button SHALL add the segment's value to values, or remove it when values holds it, and emit change exactly once with the new values; values may become empty. |
SEG-3 | WHILE a segment's disabled is true THE segmented button SHALL NOT select or clear it or emit change for it, SHALL skip it with the arrow keys, SHALL NOT make it the Tab stop and SHALL expose the disabled state to assistive technology. |
SEG-4 | WHILE a segment is hovered, keyboard-focused or pressed THE segmented button SHALL render its container, label, icon, check, elevation and opacity from the component tokens of its condition (selected or unselected) in the highest-precedence active state, with precedence pressed over focused over hovered; focus gained by pointer or touch SHALL NOT select the focused state. A part the interaction states recolor changes over the component's state motion; only a change of condition uses the selection motion (SEG-16). |
SEG-5 | WHEN a segment receives keyboard focus THE segmented button SHALL show the focus ring inside the segment's container, where the set's outline and the neighbouring segments cannot cover or clip it, without animation; focus gained by pointer or touch SHALL NOT show it. |
SEG-6 | WHERE the set is shorter than the minimum target THE segmented button SHALL extend each segment's hit area above and below the set to sys.target.touch for touch input and sys.target.pointer for fine pointers without changing its visual size, and SHALL make each segment at least as wide as that target, because neighbouring segments cannot extend a hit area over each other; a platform that cannot tell the input type SHALL use sys.target.touch. |
SEG-7 | WHILE a segment's disabled is true THE segmented button SHALL render its container, label, icon, check, elevation and opacity from the disabled component tokens of its condition; the set's outline and the dividers SHALL keep their colors, so that the set keeps a visible boundary. |
SEG-8 | WHEN size names a value that the active design system does not have THE segmented button SHALL render with the default value's tokens, and in debug builds report the unknown value. |
SEG-9 | WHEN the segment is pressed by pointer, touch, Enter or Space THE segment SHALL show the pressed state without delay and SHALL keep it visible for at least sys.motion.duration.press-hold, even when the press ends sooner. |
SEG-10 | WHILE pressed THE segment SHALL answer as sys.behavior.pressed-feedback names: overlay applies the pressed tokens to the whole container at once; ripple grows the pressed state layer from the point of contact (from the center for keyboard activation); dim applies the pressed opacity to the whole control and draws no state layer; none draws no answer to the press. Under ripple and dim only the container color stays with the state under the press; label, icon, check, elevation, opacity and shape still come from the pressed tokens. Under none every part stays with the state under the press. The ripple grows over comp.segmented-button.motion.feedback-duration with comp.segmented-button.motion.state-easing, fades over the state duration of its size (comp.segmented-button.motion.state-duration.small, .medium or .large) with comp.segmented-button.motion.state-easing once the press has ended and press-hold has passed, and appears whole where motion is reduced. |
SEG-11 | THE segment SHALL ease its container corners by sys.shape.corner-smoothing (0 is a quarter circle, 0.6 the iOS continuous corner; a platform with only the OS curve draws it for any amount above 0) and show its keyboard focus as sys.behavior.focus-style names (ring or glow); a platform that cannot draw a choice SHALL fall back to the first value and state that in its README. |
SEG-12 | THE segmented button SHALL render a segment from the selected condition (comp.segmented-button.selected.container.color and the other selected parts) WHILE selection is single and value equals the segment's value, or selection is multiple and values holds it, and every other segment from the unselected condition (comp.segmented-button.unselected.container.color and so on); WHEN value or values names no segment THE segmented button SHALL select nothing for that name, and WHEN a segment's value is empty or repeats another segment's THE segmented button SHALL still render it and treat the first segment with a value as the one that value selects; in debug builds it SHALL report each of these. |
SEG-13 | THE segmented button SHALL lay its segments out in one row, in order, in a set at least the container height of its size tall (comp.segmented-button.container.height.medium for medium, and so on), filled with comp.segmented-button.set.color, with outer corners of comp.segmented-button.set.shape, an outline of comp.segmented-button.outline.width in comp.segmented-button.outline.color inside its edge, and its segments inset from that edge by comp.segmented-button.set.padding; the outer corners of the first and last segment SHALL be the set's corners less set.padding, so that the two curves stay concentric, and every other corner of a segment SHALL be comp.segmented-button.container.shape; each segment SHALL clip its fill, state layer and ripple to its own shape, and the set SHALL NOT clip a segment's elevation. |
SEG-14 | THE segmented button SHALL give every segment the same width: the widest segment's content plus the padding of its size on each side (comp.segmented-button.container.padding-inline.medium for medium, and so on), a segment's content being its leading glyph (its icon, or the check where one would be drawn), the gap of its size (comp.segmented-button.container.gap.medium, and so on) and its label, measured as if the segment were selected, so that selecting a segment never changes a width; WHERE the layout gives the set more width THE segmented button SHALL divide it equally among the segments, and WHERE less, it SHALL divide what it has equally and let labels wrap onto more lines rather than truncate, growing every segment to the tallest, with at least the padding-block of its size (comp.segmented-button.container.padding-block.medium, and so on) above and below. |
SEG-15 | THE segmented button SHALL centre a segment's content in it, the leading glyph first; SHALL set the label in the label style of its size (comp.segmented-button.label.typescale.medium, and so on) and the label color of its condition and state; and SHALL draw the icon in the icon color of its condition and state at the icon size of its size (comp.segmented-button.icon.size.medium, and so on) through the icon helper, with the family and fill of the segment's condition (selected for a selected segment, otherwise unselected), sys.icon.weight and an optical size clamped between sys.icon.optical-size.min and sys.icon.optical-size.max. |
SEG-16 | WHILE a segment is selected and its label is drawn THE segmented button SHALL draw the glyph check of the system's icon set in the leading position, in place of the segment's icon when it has one, as the filter chip draws its check (CHP-13, CHP-14), at the check size of its size (comp.segmented-button.check.size.medium, and so on) in the icon color of the selected condition, with sys.icon.family.selected, sys.icon.fill.selected, the weight comp.segmented-button.check.weight (not sys.icon.weight: the check is a control's own mark drawn on the selected fill, as the checkbox's is, CHK-12) and an optical size clamped between sys.icon.optical-size.min and sys.icon.optical-size.max, and SHALL NOT mirror it when the layout direction is right-to-left; the weight SHALL change the stroke of the glyph only, the check's box staying its check size; THE segmented button SHALL draw no mark of its own (no path, shape or character of its own for the check). An icon-only segment SHALL keep its icon when selected and draw no check; WHILE the check size of the segment's size is 0 THE segmented button SHALL draw no check, reserve no room for it, and keep the icon. WHEN a segment becomes selected or unselected THE segmented button SHALL fade the check in or out (a glyph is not drawn along a path), cross-fading it with the icon where the segment has one, and change the segment's colors and elevation over comp.segmented-button.motion.selection-duration with comp.segmented-button.motion.selection-easing, re-centring the content as the check comes and goes, and SHALL show the new condition at once where motion is reduced. |
SEG-17 | THE segmented button SHALL draw a line of comp.segmented-button.divider.width in comp.segmented-button.divider.color between each two neighbouring segments, taking that width between them and running from the set's top padding to its bottom padding; the line SHALL keep its color and full opacity whatever the state or condition of either segment, and SHALL be hidden from assistive technology. |
SEG-18 | WHILE selection is single THE segmented button SHALL be one Tab stop — the selected segment, or the first enabled segment while none is selected; WHILE a segment has keyboard focus Right Arrow and Down Arrow SHALL move focus to the next enabled segment and Left Arrow and Up Arrow to the previous one, wrapping at the ends, and Home and End to the first and last enabled segment, and each move SHALL also select the segment it reaches and emit change, as a radio group does; in a right-to-left layout Left Arrow SHALL move to the next segment and Right Arrow to the previous. |
SEG-19 | WHILE selection is multiple THE segmented button SHALL be one Tab stop — the segment that had focus last, or else the first selected segment, or else the first enabled segment; WHILE a segment has keyboard focus Right Arrow and Down Arrow SHALL move focus to the next enabled segment and Left Arrow and Up Arrow to the previous one, wrapping at the ends, and Home and End to the first and last enabled segment, without changing the selection, and Space or Enter SHALL switch the focused segment (SEG-2); in a right-to-left layout Left Arrow SHALL move to the next segment and Right Arrow to the previous. |
SEG-20 | WHILE selection is single THE segmented button SHALL expose the set as a radio group named by label and each segment as a radio with its checked state; WHILE selection is multiple THE segmented button SHALL expose the set as a group named by label and each segment as a toggle button with its pressed state, as a toggle Button is; in both, each segment SHALL be named by its own label whether or not it is drawn, over a name the product gives the segment on the element (aria-label or aria-labelledby) and expose its position and the number of segments, and the icons, the check, the dividers and the outline SHALL be hidden. |
SEG-21 | WHEN the layout direction is right-to-left THE segmented button SHALL order the segments from the right, mirror each segment's content (the glyph to the right of the label) and apply its paddings by logical start and end, and SHALL grow a ripple from the point of contact as in left-to-right. |
SEG-22 | WHILE a segment's label is empty and the product gives the segment a name of its own on the element — aria-label, or aria-labelledby naming an element — THE segmented button SHALL expose that name as the segment's accessible name; WHILE a segment's label is empty and the product gives it none THE segmented button SHALL still render the segment, and in debug builds report that it has no accessible name; WHILE a segment's labelHidden is true and its icon is empty THE segmented button SHALL draw the label anyway and in debug builds report the segment; WHILE the set's label is empty, or the set holds fewer than two or more than five segments, THE segmented button SHALL still render and in debug builds report it. |
SEG-23 | WHEN the colors or the elevation of a segment change between interaction states THE segmented button SHALL animate them over the state duration of its size (comp.segmented-button.motion.state-duration.small, .medium or .large) with comp.segmented-button.motion.state-easing, and SHALL change them at once where motion is reduced. |
SEG-24 | WHILE a segment is selected THE segmented button SHALL cast the elevation of its condition and state (comp.segmented-button.selected.container.elevation at rest, and so on) outside the segment and above its neighbours; THE segmented button SHALL NOT position itself or draw anything outside the set but that elevation. |
SEG-25 | IF the icon set cannot draw the check yet (its font is still loading or failed to load) THE segmented button SHALL draw nothing in the check's place, never the glyph's name as text, SHALL keep the room SEG-14 measures for it so that no width changes, SHALL still expose the segment's selected state, and SHALL show the check once the icon set can draw it, without the selection motion of SEG-16. |
SEG-26 | THE segmented button SHALL take its layout direction from where it is used — the direction of the nearest ancestor that sets one, and the platform's own where none does — and SHALL have no direction setting of its own; WHEN that direction changes while the segmented button is shown THE segmented button SHALL draw itself for the new direction at once, without a motion of its own, keeping its selection and its focus. |
SEG-27 | WHERE the layout direction is right-to-left THE segmented button SHALL draw a segment's icon mirrored left to right exactly when the system's icon set marks that glyph's name as mirrored or the product forces mirroring for that use, and unmirrored when the product forbids it: the icon helper mirrors the glyph inside its own box, about the box's vertical centre line, changing neither its place, size, color and fill nor the order SEG-21 gives. THE segmented button SHALL NOT mirror a glyph itself, and SHALL NOT mirror content the product gives as an image or a view of its own rather than by a glyph's name. The check of a selected segment is never mirrored (SEG-16). |
SEG-28 | THE segmented button SHALL lay out a segment's label as text of its own direction, isolated from the text around it: each takes the base direction of its first strong character, or the layout direction where it has none, so that a left-to-right word, a number with its sign or unit, a telephone number and an address keep their own order in a right-to-left layout and reorder nothing beside them; THE segmented button SHALL still place each label and align its lines by the layout direction, not by the text's own. |
SEG-29 | WHERE the platform has ARIA attributes (the web), WHEN the product sets an aria- attribute on a segment's host, by the attribute or by the ARIA property that reflects it, THE segmented button SHALL move it to the data-aria- attribute of the same name, so that the host is no second node with its name, description or state, and SHALL expose it on the element that carries the segment's role — an id reference by the elements it names in the host's tree or a tree around it, an error message as part of the description while the segment is invalid — except those a segment owns (aria-checked, aria-pressed, aria-disabled), which it SHALL move and not expose. WHEN the product removes the aria- attribute or its data-aria- twin, or sets the ARIA property that reflects it (ariaLabel, ariaDescribedByElements…) to null, THE segmented button SHALL take it off that element. WHEN the product sets an aria- attribute a segment owns THE segmented button SHALL report it in debug builds. The set's host carries its radio group or group role itself (SEG-20), so what the product writes on it is not moved, but for a name: WHILE the set's label is not empty THE segmented button SHALL hold the product's aria-label and aria-labelledby on that host as their data-aria- twins, so that label is the set's whole name although the platform gives aria-labelledby the precedence, and WHEN label is emptied SHALL give them back as they were written; WHILE it is empty a name the product gives so is the set's name and SHALL NOT be reported as having none in debug builds (SEG-22); WHEN the product removes one, or its data-aria- twin, or sets the ARIA property that reflects it to null, THE segmented button SHALL take it away. |
Correspondencia de nombres por plataforma
Paridad no significa API idénticas. Cada plataforma expresa el mismo contrato con su propio estilo.
| Especificación | Web | SwiftUI | Jetpack Compose | Flutter | React Native |
|---|---|---|---|---|---|
| Componente | tanrei-segmented-button | TanreiSegmentedButton | TanreiSegmentedButton | TanreiSegmentedButton | SegmentedButton |
selection · Propiedad | selection | selection | selectionMode | multiSelectionEnabled | selectionMode |
value · Propiedad | value | selection | selectedValue | selected | value |
values · Propiedad | values | selection | selectedValues | selected | values |
size · Propiedad | size | size | size | size | size |
label · Propiedad | label | label | contentDescription | semanticLabel | accessibilityLabel |
change · Evento | change | selection | onSelectionChange | onSelectionChanged | onSelectionChange |
| Notas | tanrei-segmented-button (selection, value, values, size, label) holds tanrei-segment children. value is an attribute and a property; values is a property (an array); the values attribute is also read, as JSON or as space-separated words, because the fixture harness writes attributes. It sets its own value or values before firing change, as a native control does. It puts role radiogroup (single) or group (multiple) and aria-label on its own element, and on each segment's inner <button> role radio with aria-checked, aria-posinset and aria-setsize (single), or aria-pressed (multiple), with a roving tabindex. A toggle button may not carry aria-posinset, so in a multiple set the row is a role="list" and each segment a role="listitem" that carries the position; ElementInternals is not used for the roles, because axe cannot see it. It is not form-associated. The check is the icon helper's check glyph in the check part (SEG-16). | TanreiSegmentedButton(_ label:, selection: Binding<V?>, size:) { TanreiSegment … } for single selection and TanreiSegmentedButton(_ label:, selection: Binding<Set<V>>, size:) { … } for multiple: the binding's type is selection, and writing it is change. SwiftUI's Picker with .pickerStyle(.segmented) is not used: its segments cannot be tokenised. A single-choice segment is a button with the .isSelected trait and its position as its accessibility value; a multiple-choice segment adds the .isToggle trait (iOS 17). Lagging behind SEG-16 and SEG-25: without an installed icon font it strokes the check as a vector of its own (TanreiChipGlyph, on the checkbox's mark geometry) instead of drawing nothing. Lagging behind SEG-16's weight (the check drawn at comp.segmented-button.check.weight): its check is drawn at sys.icon.weight. | One composable for both selections (Material's SingleChoiceSegmentedButtonRow and MultiChoiceSegmentedButtonRow in one): TanreiSegmentedButton(selectionMode, selectedValue, selectedValues, onSelectionChange, size, contentDescription) { TanreiSegment(…) }. State hoisting: the caller keeps selectedValue or selectedValues and moves it from onSelectionChange. The row is a selectableGroup(); a single-choice segment is selectable(role = Role.RadioButton) and a multiple-choice one toggleable(role = Role.Button), as the filter chip is. Compose has no radio group role. onSelectionChange is (Set<String>) -> Unit for both selections: a single choice passes a set of one (as the list does). Lagging behind SEG-16 and SEG-25: without an installed icon font it strokes the check as a vector of its own (TanreiDrawnGlyph, tanreiCheckPath) instead of drawing nothing. Lagging behind SEG-16's weight (the check drawn at comp.segmented-button.check.weight): its check is drawn at sys.icon.weight. | Shaped like Flutter's SegmentedButton<T> but built with the widgets library, without Material: TanreiSegmentedButton<T>(segments:, selected: Set<T>, onSelectionChanged:, multiSelectionEnabled:, size:, semanticLabel:). selected holds zero or one value while multiSelectionEnabled is false; the caller moves it from onSelectionChanged. A single-choice segment is Semantics(inMutuallyExclusiveGroup: true, checked:) and a multiple-choice one Semantics(button: true, toggled:), inside a Semantics(container: true, label:) for the set. A single-choice set is exposed with SemanticsRole.radioGroup, named by semanticLabel (SEG-20). Lagging behind SEG-25: it writes the check as the Material Symbols code point U+E5CA (tanreiCheckGlyph), and without the icon font it draws whatever the fallback face has for that code point instead of nothing. Lagging behind SEG-16's weight (the check drawn at comp.segmented-button.check.weight): its check is drawn at sys.icon.weight. | <SegmentedButton items={Segment[]} selectionMode value | values onSelectionChange size accessibilityLabel>; controlled, the caller moves value or values from onSelectionChange. The set has the radiogroup role (single) or the group role (multiple); each segment the radio role with accessibilityState.checked, or the button role with accessibilityState.selected, as a toggle Button is. The arrow keys work where a hardware keyboard is attached. Lagging behind SEG-25: it writes the ligature check into the glyph box, and without the icon font it prints the word instead of drawing nothing. Lagging behind SEG-16's weight (the check drawn at comp.segmented-button.check.weight): its check is drawn at sys.icon.weight. |
Tokens
| Token | Alias de | Valor resuelto (claro) |
|---|---|---|
--tanrei-comp-segmented-button-check-size-large | sys.icon.extra-small | 16px |
--tanrei-comp-segmented-button-check-size-medium | sys.icon.extra-small | 16px |
--tanrei-comp-segmented-button-check-size-small | sys.icon.extra-small | 16px |
--tanrei-comp-segmented-button-check-weight | sys.icon.mark.weight | 500 |
--tanrei-comp-segmented-button-container-gap-large | sys.space.space100 | 8px |
--tanrei-comp-segmented-button-container-gap-medium | sys.space.space100 | 8px |
--tanrei-comp-segmented-button-container-gap-small | sys.space.space100 | 8px |
--tanrei-comp-segmented-button-container-height-large | — | 40px |
--tanrei-comp-segmented-button-container-height-medium | — | 36px |
--tanrei-comp-segmented-button-container-height-small | — | 32px |
--tanrei-comp-segmented-button-container-padding-block-large | — | 6px |
--tanrei-comp-segmented-button-container-padding-block-medium | — | 6px |
--tanrei-comp-segmented-button-container-padding-block-small | — | 6px |
--tanrei-comp-segmented-button-container-padding-inline-large | sys.space.space200 | 16px |
--tanrei-comp-segmented-button-container-padding-inline-medium | sys.space.space175 | 14px |
--tanrei-comp-segmented-button-container-padding-inline-small | sys.space.space150 | 12px |
--tanrei-comp-segmented-button-container-shape | sys.shape.corner.none | 0px |
--tanrei-comp-segmented-button-disabled-container-shape | — | 0px |
--tanrei-comp-segmented-button-disabled-opacity | — | 1 |
--tanrei-comp-segmented-button-divider-color | sys.color.outline | |
--tanrei-comp-segmented-button-divider-width | sys.border.hairline | 1px |
--tanrei-comp-segmented-button-focused-container-shape | — | 0px |
--tanrei-comp-segmented-button-focused-opacity | — | 1 |
--tanrei-comp-segmented-button-hovered-container-shape | — | 0px |
--tanrei-comp-segmented-button-hovered-opacity | — | 1 |
--tanrei-comp-segmented-button-icon-size-large | sys.icon.extra-small | 16px |
--tanrei-comp-segmented-button-icon-size-medium | sys.icon.extra-small | 16px |
--tanrei-comp-segmented-button-icon-size-small | sys.icon.extra-small | 16px |
--tanrei-comp-segmented-button-motion-feedback-duration | sys.motion.role.feedback | 450ms |
--tanrei-comp-segmented-button-motion-selection-duration | sys.motion.role.selection.mark | 250ms |
--tanrei-comp-segmented-button-motion-selection-easing | sys.motion.easing.state | cubic-bezier(0.2, 0, 0, 1) |
--tanrei-comp-segmented-button-motion-state-duration-large | sys.motion.role.state.large | 250ms |
--tanrei-comp-segmented-button-motion-state-duration-medium | sys.motion.role.state.default | 250ms |
--tanrei-comp-segmented-button-motion-state-duration-small | sys.motion.role.state.compact | 200ms |
--tanrei-comp-segmented-button-motion-state-easing | sys.motion.easing.state | cubic-bezier(0.2, 0, 0, 1) |
--tanrei-comp-segmented-button-outline-color | sys.color.outline | |
--tanrei-comp-segmented-button-outline-width | sys.border.hairline | 1px |
--tanrei-comp-segmented-button-pressed-container-shape | — | 0px |
--tanrei-comp-segmented-button-pressed-opacity | — | 1 |
--tanrei-comp-segmented-button-selected-container-color | sys.color.secondary-container | |
--tanrei-comp-segmented-button-selected-container-elevation | sys.elevation.level0 | |
--tanrei-comp-segmented-button-selected-disabled-container-color | — | |
--tanrei-comp-segmented-button-selected-disabled-container-elevation | — | |
--tanrei-comp-segmented-button-selected-disabled-icon-color | — | |
--tanrei-comp-segmented-button-selected-disabled-label-color | — | |
--tanrei-comp-segmented-button-selected-disabled-state-layer-color | — | |
--tanrei-comp-segmented-button-selected-focused-container-color | — | |
--tanrei-comp-segmented-button-selected-focused-container-elevation | — | |
--tanrei-comp-segmented-button-selected-focused-icon-color | — | |
--tanrei-comp-segmented-button-selected-focused-label-color | — | |
--tanrei-comp-segmented-button-selected-focused-state-layer-color | — | |
--tanrei-comp-segmented-button-selected-hovered-container-color | — | |
--tanrei-comp-segmented-button-selected-hovered-container-elevation | — | |
--tanrei-comp-segmented-button-selected-hovered-icon-color | — | |
--tanrei-comp-segmented-button-selected-hovered-label-color | — | |
--tanrei-comp-segmented-button-selected-hovered-state-layer-color | — | |
--tanrei-comp-segmented-button-selected-icon-color | sys.color.on-secondary-container | |
--tanrei-comp-segmented-button-selected-label-color | sys.color.on-secondary-container | |
--tanrei-comp-segmented-button-selected-pressed-container-color | — | |
--tanrei-comp-segmented-button-selected-pressed-container-elevation | — | |
--tanrei-comp-segmented-button-selected-pressed-icon-color | — | |
--tanrei-comp-segmented-button-selected-pressed-label-color | — | |
--tanrei-comp-segmented-button-selected-pressed-state-layer-color | — | |
--tanrei-comp-segmented-button-selected-state-layer-color | comp.segmented-button.selected.label.color | |
--tanrei-comp-segmented-button-set-color | — | |
--tanrei-comp-segmented-button-set-padding | sys.space.space0 | 0px |
--tanrei-comp-segmented-button-set-shape | sys.shape.corner.small | 6px |
--tanrei-comp-segmented-button-unselected-container-color | — | |
--tanrei-comp-segmented-button-unselected-container-elevation | sys.elevation.level0 | |
--tanrei-comp-segmented-button-unselected-disabled-container-color | — | |
--tanrei-comp-segmented-button-unselected-disabled-container-elevation | — | |
--tanrei-comp-segmented-button-unselected-disabled-icon-color | — | |
--tanrei-comp-segmented-button-unselected-disabled-label-color | — | |
--tanrei-comp-segmented-button-unselected-disabled-state-layer-color | — | |
--tanrei-comp-segmented-button-unselected-focused-container-color | — | |
--tanrei-comp-segmented-button-unselected-focused-container-elevation | — | |
--tanrei-comp-segmented-button-unselected-focused-icon-color | — | |
--tanrei-comp-segmented-button-unselected-focused-label-color | — | |
--tanrei-comp-segmented-button-unselected-focused-state-layer-color | — | |
--tanrei-comp-segmented-button-unselected-hovered-container-color | — | |
--tanrei-comp-segmented-button-unselected-hovered-container-elevation | — | |
--tanrei-comp-segmented-button-unselected-hovered-icon-color | — | |
--tanrei-comp-segmented-button-unselected-hovered-label-color | — | |
--tanrei-comp-segmented-button-unselected-hovered-state-layer-color | — | |
--tanrei-comp-segmented-button-unselected-icon-color | sys.color.on-surface-variant | |
--tanrei-comp-segmented-button-unselected-label-color | sys.color.on-surface | |
--tanrei-comp-segmented-button-unselected-pressed-container-color | — | |
--tanrei-comp-segmented-button-unselected-pressed-container-elevation | — | |
--tanrei-comp-segmented-button-unselected-pressed-icon-color | — | |
--tanrei-comp-segmented-button-unselected-pressed-label-color | — | |
--tanrei-comp-segmented-button-unselected-pressed-state-layer-color | — | |
--tanrei-comp-segmented-button-unselected-state-layer-color | comp.segmented-button.unselected.label.color | |
--tanrei-comp-segmented-button-label-typescale-large | sys.typescale.label | 500 14px/1.4286 |
--tanrei-comp-segmented-button-label-typescale-medium | sys.typescale.label | 500 14px/1.4286 |
--tanrei-comp-segmented-button-label-typescale-small | sys.typescale.label | 500 14px/1.4286 |
Fixtures
Representaciones canónicas. Todas las plataformas capturan cada fixture con el mismo identificador para poder comparar los resultados.
size: small (1)
small
selection: single value: week size: small label: Range items: 3 size: medium (7)
single
selection: single value: week label: Range items: 3 single-none
selection: single label: Range items: 3 multiple
selection: multiple values: ["mon","tue","thu"] label: Days items: 4 icons
selection: single value: grid label: View items: 3 icon-only
selection: single value: center label: Text alignment items: 3 disabled
selection: single value: day label: Range items: 3 selected-disabled
selection: single value: month label: Range items: 3 size: large (1)
large
selection: single value: week size: large label: Range items: 3 Generado a partir de specs/segmented-button.spec.json, tokens/comp/segmented-button.tokens.json, design/tokens/
Usa un botón segmentado cuando una pregunta pequeña tiene unas pocas respuestas fijas y conviene que las personas las vean todas a la vez: el intervalo de un gráfico, la disposición de una lista, la alineación de un párrafo, los días en que se repite un recordatorio. El efecto debe verse de inmediato, porque con la selección única las teclas de flecha eligen a medida que se mueven.
Caben de dos a cinco opciones. Con más de cinco, usa un menú o una lista. Cuando la elección es la tarea principal de un formulario, los botones de opción se leen mejor. Cuando la respuesta cambia qué contenido llena la pantalla, usa pestañas.
Los cuatro colocan unas pocas cosas relacionadas en una fila, así que es fácil confundirlos. Se diferencian en lo que hace una pulsación y en cómo se recorren con el teclado.
| Componente | Qué es | Selección | Teclado | Úsalo para |
|---|---|---|---|---|
| Botón segmentado | Un solo control: de dos a cinco opciones unidas que responden a una pregunta. | Propia, por valor: una opción o varias. | Una sola parada de tabulación. Las teclas de flecha se mueven entre las opciones y, con la selección única, también eligen. | Un ajuste con unas pocas respuestas fijas que se aplica al instante: Día, Semana, Mes; izquierda, centro, derecha. |
| Grupo de botones | Una fila o una columna de botones independientes, separados o unidos en una sola forma. | Ninguna. Un botón conmutador del grupo conserva su propio estado de activado o desactivado. | Cada botón es su propia parada de tabulación. | Acciones relacionadas: Cancelar, Guardar borrador, Publicar; Negrita, Cursiva y Subrayado como conmutadores independientes. |
| Chips | Controles pequeños e independientes en una fila que salta de línea o se desplaza. | Cada chip de filtro está activado o desactivado por sí mismo. | Cada chip es su propia parada de tabulación. | Filtros encima de una lista, respuestas sugeridas, elementos que la persona ha introducido. |
| Pestañas | Vistas de un mismo tema, cada una con su propio panel. | Una pestaña: la vista en pantalla. | Una sola parada de tabulación. Las teclas de flecha mueven y seleccionan. | Cambiar qué contenido se muestra: Resumen, Actividad, Configuración. |
Una prueba rápida: si al pulsarlo hace algo, es un grupo de botones. Si define un valor, es un botón segmentado, o chips cuando las opciones son muchas o independientes. Si cambia el contenido de debajo, son pestañas.
- Única (
selection="single", el valor predeterminado) es un grupo de botones de opción. Elegir un segmento desmarca el anterior. Pulsar de nuevo el segmento elegido no hace nada, así que una elección única no se puede borrar desde su propio segmento. El conjunto puede empezar sin nada elegido (valuevacío), para un formulario que debe mostrar que todavía no se ha elegido nada. - Múltiple es un grupo de botones conmutadores. Cada segmento se activa y se desactiva, y el conjunto puede quedarse sin ninguno. Si tu producto necesita al menos uno, no apliques un cambio que deje el conjunto vacío.
El conjunto no tiene un disabled propio. Deshabilita los segmentos uno a uno. Un segmento deshabilitado conserva su lugar y su contorno, y las teclas de flecha lo saltan.
- Un segmento seleccionado muestra una marca de verificación antes de su etiqueta, en lugar de su icono cuando lo tiene, de modo que la selección nunca se comunica solo con el relleno. Un segmento de solo icono conserva su icono y lo dibuja relleno. Un sistema de diseño puede poner el tamaño de la marca en 0: entonces no dibuja ninguna marca y muestra la selección con el relleno y la elevación.
- Todos los segmentos son tan anchos como el más ancho, medido como si estuviera seleccionado, así que la aparición de la marca nunca mueve a un vecino. Con menos espacio, las etiquetas saltan de línea y todos los segmentos crecen hasta la altura del más alto. Nunca se truncan.
labelHiddendibuja solo el icono. La etiqueta sigue siendo obligatoria, porque continúa siendo el nombre accesible del segmento.- El tamaño define la altura del conjunto. Los tamaños no coinciden con las alturas del botón en todos los pasos (en el preajuste
m3-like, small y medium coinciden con los del botón y large es más bajo), así que empareja un conjunto con los botones que tiene al lado por la altura, no por el nombre del tamaño.
- Da al conjunto una etiqueta que formule la pregunta a la que responden sus opciones: «Intervalo», «Alineación del texto».
- Limita las etiquetas a una o dos palabras, con la misma forma gramatical: Día, Semana, Mes.
- Da un icono a todos los segmentos de un conjunto, o a ninguno.
- Elige un valor inicial cuando haya un valor predeterminado razonable, para que el control nunca parezca sin responder.
- No uses un botón segmentado para acciones. Un segmento es una elección y no emite ningún clic. Usa un grupo de botones.
- No lo uses para cambiar entre vistas que llenan cada una la pantalla. Usa pestañas.
- No pongas más de cinco segmentos en un conjunto, ni etiquetas de longitudes muy distintas. Todos los segmentos toman el ancho del más ancho.
- No cambies la etiqueta de un segmento según su estado. La selección se anuncia por separado.
- Rol
radiogroup- Etiquetado
- The set is named by label: the question its options answer. Each segment is named by its own label, drawn or not (labelHidden). Icons, the check, the dividers and the outline are decorative: a segment's state is announced from its checked or pressed state, never from the check.
- Objetivo mínimo
- El área de pulsación cumple el tamaño mínimo de objetivo aunque el tamaño visual sea menor. minimum 32px · pointer 44px · spacing 8px · touch 48px
Teclado
| Teclas | Acción |
|---|---|
| Tab / Shift+Tab | Moves focus into the set (to the selected segment, the last focused one, or the first enabled one) and out of it. |
| Right Arrow / Down Arrow | Moves focus to the next enabled segment, wrapping; with single selection it also selects it (Left Arrow in right-to-left layouts). |
| Left Arrow / Up Arrow | Moves focus to the previous enabled segment, wrapping; with single selection it also selects it (Right Arrow in right-to-left layouts). |
| Home / End | Moves focus to the first or last enabled segment; with single selection it also selects it. |
| Enter / Space | Selects the focused segment (single) or switches it on or off (multiple). |
Notas
- Single selection is a radio group: arrow keys move and select at once, as the radio button and tabs do, because a segment shows its effect without a noticeable delay. Multiple selection is a group of toggle buttons with one Tab stop: arrow keys only move focus, and Space or Enter switches.
- Selection is the set's: value or values holds the selected segments' values, and change carries the new ones. A segment's disabled is its own.
- iOS has no radio role: a segment of a single-choice set is a button with the selected trait and its position ("2 of 3") in its accessibility value, as the radio button is. Compose has no radio group role; the set is a selectable group and each segment `Role.RadioButton` (single) or a toggleable `Role.Button` (multiple), as the filter chip is.
- A segmented button chooses among options of one setting. Actions belong to a button group; switching views of one subject belongs to tabs.
- Text size does not clip a segment: labels wrap and every segment grows to the tallest. The icon is not text and keeps its size.
- How a state looks is a value decision of the active design system; components read the state's tokens and never compute the effect themselves.
Generado a partir de specs/segmented-button.spec.json, tokens/sys/measure.tokens.json
- Con la selección única, el conjunto es un grupo de botones de opción que recibe su nombre de su etiqueta, y cada segmento es un botón de opción con su estado marcado. Con la selección múltiple, el conjunto es un grupo que recibe su nombre de su etiqueta, y cada segmento es un botón conmutador con su estado pulsado.
- Cada segmento recibe su nombre de su propia etiqueta, se dibuje o no, y expone su posición y el número de segmentos. Los iconos, la marca de verificación, los divisores y el contorno quedan ocultos. El estado nunca se anuncia a partir de la marca.
- El conjunto es una sola parada de tabulación: el segmento seleccionado, o el último que tuvo el foco en la selección múltiple, o, si no, el primero habilitado. Las teclas de flecha pasan al segmento habilitado siguiente o anterior y dan la vuelta al llegar al final, e Inicio y Fin llevan a los extremos. Con la selección única, cada movimiento también selecciona. Con la selección múltiple, Espacio y Enter conmutan el segmento con foco. En un diseño de derecha a izquierda, Flecha izquierda pasa al segmento siguiente.
- Las teclas de flecha saltan los segmentos deshabilitados, que nunca son la parada de tabulación y se exponen como deshabilitados.
- El área de pulsación de cada segmento se extiende por encima y por debajo del conjunto hasta el objetivo mínimo, y cada segmento tiene al menos el ancho de un objetivo, porque los vecinos no pueden extenderse unos sobre otros.
- El indicador de foco se dibuja dentro del segmento con foco, donde el contorno y los vecinos no pueden taparlo. Solo se muestra para el foco del teclado.
- Con tamaños de texto mayores, las etiquetas saltan de línea y todos los segmentos crecen hasta la altura del más alto. El icono conserva su tamaño.
- Las compilaciones de depuración notifican un conjunto o un segmento sin etiqueta, una etiqueta oculta sin icono, un valor o unos valores que no nombran ningún segmento, un valor de segmento vacío o repetido y un conjunto con menos de dos o más de cinco segmentos.
Carencias conocidas por plataforma:
- En la web, un conjunto de elección múltiple da a cada segmento su posición mediante una lista que envuelve los segmentos, porque un botón conmutador no puede llevar una posición propia.
- SwiftUI no tiene un rol de grupo de botones de opción. El conjunto es un contenedor que recibe su nombre de su etiqueta. Un segmento de un conjunto de elección única es un botón con el rasgo de seleccionado y su posición («2 of 3») como valor, solo en inglés por ahora. Un segmento de un conjunto de elección múltiple es un conmutador y no indica ninguna posición, porque un valor propio sustituiría el activado o desactivado del conmutador.
- SwiftUI: el conjunto ocupa el ancho que se le ofrece, como hace el selector segmentado de SwiftUI.
.fixedSize(horizontal: true, vertical: false)mantiene su ancho natural. La sombra y el anillo de foco de un segmento usan su esquina más grande en todas las esquinas. Un SF Symbol dado como icono no cambia a su forma rellena al seleccionarse: pasa tú el símbolo.fill. Las teclas de flecha se prueban como reglas, no con un teclado en el simulador. - Compose no tiene un rol de grupo de botones de opción. El conjunto es un grupo seleccionable, y cada segmento es un botón de opción (single) o un botón conmutable (multiple), como el chip de filtro.
- Flutter no expone ni la posición de un segmento ni el número de segmentos, y un conjunto de elección múltiple es un contenedor que recibe su nombre de su etiqueta en lugar de un grupo, porque la semántica de Flutter no tiene ninguna de las dos propiedades.
- React Native: los anchos iguales salen de medir cada etiqueta después de la primera pasada de diseño, así que un conjunto cuyo padre sea más estrecho que él en el primer fotograma puede tomar un ancho menor que el de su etiqueta más ancha. Las teclas de flecha en un teclado físico, y la sombra de la selección elevada sobre sus vecinos en Android, no se han comprobado en un dispositivo.
- Con el sistema
cupertino, los conjuntos small y medium miden 30 y 34 de alto en lugar de 28 y 32, y las esquinas interiores de los segmentos de los extremos son más redondeadas que las exteriores. Ambas cosas esperan una decisión de token o de especificación.
- Da una etiqueta al conjunto y a cada segmento, incluidos los segmentos de solo icono.
- Haz que el efecto de una elección se vea al instante, cerca del control. Con la selección única, quien usa el teclado elige al moverse, así que un efecto lento hace que las teclas de flecha parezcan atascadas. Si tiene que tardar, muestra el progreso donde aparecerá el resultado.
- Indica cerca de los segmentos deshabilitados el motivo cuando no sea obvio por qué no se pueden elegir.
- En la web, el botón segmentado no es un control de formulario. Para enviar su valor con un formulario, cópialo en un input oculto desde
change.