bug: IonPopover keyboardClose={false} does not prevent keyboard dismissal since ionic 8.7.4 #31199

Activity

1. ionitron-bot

   added

   triage

   on Jun 8, 2026
2. beanscg commented on Jun 9, 2026

   

   beanscg

   on Jun 9, 2026

   More actions

   Bean Labs took a source pass. core/src/components/popover/popover.tsx still exposes @Prop() keyboardClose = true, so the regression is about whether the dismiss/open path respects an explicit false, not whether the prop exists.

   A minimal fix test would mount an input plus ion-popover keyboard-close="false", open the popover, and assert the keyboard interaction path does not call the keyboard-close utility on dismiss/open transitions. That keeps the test around the component contract instead of the app-level repro.

   No PR opened from this pass.
3. Pablosornp commented on Aug 25, 2026

   

   Pablosornp

   on Aug 25, 2026

   Author

   More actions

   Hi! Any estimation on where this issue might be at least triaged? This bug must be affecting other users.
4. thetaPC commented on Oct 20, 2026

   

   thetaPC

   on Oct 20, 2026

   Contributor

   More actions

   Thanks for the report, and sorry for the delay.

   Verified on 9.0.8. When a popover is presented, Ionic now blurs whatever element had focus before the overlay opens, and it does this before checking keyboardClose. So with keyboardClose={false} the textarea still loses focus, and on mobile the keyboard closes with it.

   Workaround, verified on 9.0.8: put focus back on the textarea from onWillPresent. That event fires in the same task as the blur, so focus returns before anything renders:

   import { useRef } from 'react';
   import { IonContent, IonPopover, IonTextarea } from '@ionic/react';
   
   export function MentionField({ isOpen }: { isOpen: boolean }) {
     const textareaRef = useRef<HTMLIonTextareaElement>(null);
   
     return (
       <>
         <IonTextarea ref={textareaRef} />
         <IonPopover
           isOpen={isOpen}
           keyboardClose={false}
           onWillPresent={() => textareaRef.current?.querySelector('textarea')?.focus()}
         >
           <IonContent className="ion-padding">Suggestions</IonContent>
         </IonPopover>
       </>
     );
   }

   Focus the inner textarea directly rather than calling setFocus(). setFocus() resolves a moment later, after the popover's focus trap is active, and the trap pulls focus into the popover. If you use a plain <textarea>, call .focus() on its ref.

   Tracked as a bug in core.

   ❤️React with ❤️1Reacted by Pablo Heras
5. thetaPC

   added

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

   type: buga confirmed bug reporta confirmed bug report

   on Oct 20, 2026
6. ionitron-bot

   removed

   triage

   on Oct 20, 2026