Skip to content

fix(select): block interaction while disabled - #17971

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

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

Conversation

@Xapollon430

Copy link
Copy Markdown

Closes #17970

Description

Bind the open Select dropdown's native inert property to the Select's disabled state. This blocks pointer and keyboard interaction with the overlay, including projected content, while the input is disabled. Re-enabling the Select restores interaction.

Motivation / Context

In Chrome, clicking Orange after the open Select became disabled changed the value from Apple to Orange and emitted one ngModelChange event. With this change the same click keeps Apple selected and emits no change.

Type of Change

  • Bug fix
  • Documentation
  • Tests
  • Changelog

Components affected

Select

How Has This Been Tested?

  • Select browser suite passed all 107 tests. The new regression failed before the fix.
  • A native Chrome click reproduced the value and event changes on upstream master and confirmed both stayed unchanged with the fix.
  • Angular library lint completed with zero errors and 917 warnings.
  • The full npm test run stopped in the library suite with 7,167 passing tests and two timeouts in grid filtering-row keyboard focus and the input mask preset. The focused Select suite passed.

Test Configuration

  • Angular 22.2.3
  • Chrome and Playwright Chromium on macOS

Screenshots / Recordings

Chrome before and after

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 Select dropdown still changes the value after the control is disabled

1 participant