Disabled date entered manually is not reverted on blur

[litvinenko-rc]

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.