Skip to content

fix(combo): block disabled dropdown interaction - #17975

Open
Xapollon430 wants to merge 1 commit into
IgniteUI:masterfrom
Xapollon430:codex/disabled-combo-dropdown
Open

Xapollon430 wants to merge 1 commit into
IgniteUI:masterfrom
Xapollon430:codex/disabled-combo-dropdown

Conversation

@Xapollon430

Copy link
Copy Markdown

Closes #17974

Description

Bind the open dropdown contents in Combo and Simple Combo to the control's disabled state using native inert. Options and other popup controls stop receiving pointer and keyboard input while disabled and become interactive again when re-enabled.

Motivation / Context

In Chrome, selecting Orange after the open control became disabled added Orange to the Combo selection and replaced Apple in Simple Combo. Both emitted a model change. With this patch, Apple remains selected and no change fires.

Type of Change

  • Bug fix
  • Documentation
  • Tests
  • Changelog

Components affected

Combo and Simple Combo

How Has This Been Tested?

  • Both new regressions failed before the patch. All 308 tests across both focused browser suites passed afterward.
  • Native Chrome pointer input confirmed the model and event count on both components before and after.
  • Scoped ESLint reported zero errors and 29 change detection warnings.
  • Full npm test stopped with 7,168 library tests passing and two timeouts, one in an existing Combo Tab test that passed in the focused suite and one in the input mask preset.

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 Combo and Simple Combo dropdowns still accept selections while disabled

1 participant