Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Change Proposal: Read-only styling for Switch, Checkbox, and Radio

Abierto
  • ¿Algo no está bien?
#331 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
accessibility, frontend

Línea de trabajo

Start by reviewing issue #272 and PR #328 to understand the existing read-only treatment for text-like controls, then locate the Switch, Checkbox, and Radio implementations. Done means the three controls support the proposed read-only interface, remain focusable and announced appropriately, prevent changes, and have an agreed visual treatment with coverage for these behaviors.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs-triage

What is being proposed?

A read-only variant for MuiSwitch, MuiCheckbox, and MuiRadio, distinct from disabled.

Why is this needed?

Follow-up from #272 / PR #328, which gave TextField/Select/Autocomplete a dedicated read-only look.

These three controls have no native readOnly support in MUI (unlike text-like inputs), and they currently have only disabled, which mutes the value and drops the control from the tab order even when the value itself still needs to be shown and announced, with no read-only treatment at all.

What will change?

  • Behaviour: enforce read-only via controlled checked + no-op onChange, since native readonly on checkbox/radio inputs doesn't block clicks
  • Accessibility: aria-readonly instead of aria-disabled, keeping the control focusable/announced
  • Visual: likely closer to full saturation than the muted --ds-surface-readonly wash used for text inputs, since the value is meaningful and being displayed, not unavailable

Interface changes (if any)

<Switch readOnly checked={value} />
<Checkbox readOnly checked={value} />
<Radio readOnly checked={value} />

Breaking change?

  • No

Next steps

A maintainer will review this issue.
If accepted, it will be marked as accepted and a PR may then be opened.

Lenguaje dominante
TypeScript
Estrellas
9
Forks
3
Merge medio
6 d 7 h
PR fusionados (30 d)
20

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DiamondLightSource/sci-react-ui

Todos los issues de DiamondLightSource/sci-react-ui

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.