Skip to content

fix(date-picker): prevent disabled calendar selections - #17977

Open
Xapollon430 wants to merge 1 commit into
IgniteUI:masterfrom
Xapollon430:codex/disabled-date-picker-calendars
Open

Xapollon430 wants to merge 1 commit into
IgniteUI:masterfrom
Xapollon430:codex/disabled-date-picker-calendars

Conversation

@Xapollon430

Copy link
Copy Markdown

Closes #17976

Description

Make the shared calendar and predefined ranges inert while the Date Picker or Date Range Picker is disabled. The default Today action follows the same disabled state. Existing dismiss actions remain available.

Motivation / Context

In Chrome, clicking November 13 after the picker became disabled changed the date in both components and emitted one model change. With this change, the original date or range stays selected and no model change fires.

Type of Change

  • Bug fix
  • Documentation
  • Tests
  • Changelog

Components affected

Date Picker and Date Range Picker

How Has This Been Tested?

  • Both new regressions failed before the patch. All 201 focused browser tests passed afterward.
  • Native Chrome pointer input confirmed the value and event count before and after in both components.
  • Scoped ESLint reported zero errors and 21 change detection warnings.
  • Full npm test stopped in the library suite with 7,168 tests passing and two failures in grid keyboard navigation. Both focused picker suites passed.

Test Configuration

  • Angular 22.2.3
  • Chrome and Playwright Chromium on macOS

Screenshots / Recordings

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Open Date Picker and Date Range Picker calendars accept selection after disabling

1 participant