bug: ion-select accepts selection after becoming disabled while open #31687

Activity

1. ionitron-bot

   added

   triage

   on Nov 3, 2026
2. thetaPC commented on Nov 3, 2026

   

   thetaPC

   on Nov 3, 2026

   Contributor

   More actions

   Thanks for the report.

   Verified on 9.0.10. ion-select checks disabled when it opens its overlay, but not when the open alert, action sheet, popover or modal commits a selection, so a pick made after disabled turns on still updates value and emits ionChange. This affects all four interfaces.

   Until a fix ships, restore the last committed value in your ionChange handler when the select is disabled. This is verified on 9.0.10 with all four interfaces:

   const select = document.querySelector('ion-select');
   let committed = select.value;
   
   select.addEventListener('ionChange', (ev) => {
     if (select.disabled) {
       select.value = committed;
       return;
     }
     committed = ev.detail.value;
     // handle the new value here
   });

   ionChange still fires for the rejected pick, so keep the disabled check in any handler that acts on the value. If your app also sets value programmatically, update committed there too.

   Tracked as a bug in core, with the fix under review in #31688.
3. thetaPC

   added

   package: core@ionic/core package@ionic/core package

   type: buga confirmed bug reporta confirmed bug report

   on Nov 3, 2026
4. ionitron-bot

   removed

   triage

   on Nov 3, 2026