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

Disabled date entered manually is not reverted on blur

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
frontend

Línea de trabajo

Start by tracing the blur path through flushFieldSubmit, triggerSubmitChange, and the popup-close handling described in the issue; compare it with the Enter path and the previous useRangeValue reset behavior. Add or update a regression test for a controlled picker with a rejected disabledDate, then verify blur restores the selected value while Enter continues to do so.

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

Descripción

Description

Since @rc-component/picker 1.12.0, manually entering a date rejected by disabledDate and then blurring the input leaves the rejected date displayed.

In 1.11.0, the input reverted to the previously selected value after blur.

Enter and blur now behave differently: pressing Enter restores the previous value, while blurring leaves the disabled date in the input.

Reproduction

Use a controlled single date picker with:

  • Moment generateConfig
  • Format: MM/DD/YYYY
  • Value: 06/15/2026
  • disabledDate rejecting dates before 06/01/2026
  • State updated only through onChange
  1. Focus the input.
  2. Replace its contents with 03/15/2026.
  3. Click outside the picker.
Expected behavior

The disabled date is rejected, and the input displays the previously selected value, 06/15/2026, consistent with version 1.11.0.

Actual behavior

The input continues to display 03/15/2026, although onChange does not accept that date and the controlled value remains 06/15/2026.

Repeating the same steps but pressing Enter instead of clicking outside restores 06/15/2026.

Minimal example
import React, { useState } from 'react';
import Picker from '@rc-component/picker';
import momentConfig from '@rc-component/picker/lib/generate/moment';
import enUS from '@rc-component/picker/lib/locale/en_US';
import moment from 'moment';

const format = 'MM/DD/YYYY';
const minDate = moment('06/01/2026', format);

export default function Example() {
  const [value, setValue] = useState(moment('06/15/2026', format));

  return (
    <Picker
      generateConfig={momentConfig}
      locale={enUS}
      format={format}
      value={value}
      disabledDate={(date) => date.isBefore(minDate, 'day')}
      onChange={setValue}
    />
  );
}
Versions verified
  • 1.11.0: previous value is restored on blur.
  • 1.12.0: disabled date remains displayed on blur.
  • 1.15.0: same behavior as 1.12.0.
Possible cause

This appears related to PR #994, which introduced useRangeValueChange.

Previously, useRangeValue reset the temporary calendar value to mergedValue after the interaction ended.

In the new flow, flushFieldSubmit calls triggerSubmitChange and closes the popup without handling its false return value. When disabledDate rejects the submission, the temporary calendar value is not reset on blur.

After Enter, the interaction is already completed when popupClose is processed, which takes the reset path and restores the previous value.

Lenguaje dominante
TypeScript
Estrellas
304
Forks
347
Merge medio
1 d 2 h
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 react-component/picker

Todos los issues de react-component/picker

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.