bug: ion-footer remains visible after sheet modal dismissal

[matejdurajka]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Ionic Framework Version

v8.x

Current Behavior

ion-footer element remains visible on screen after a sheet modal has been dismissed

This issue appears to only occur on mobile screen sizes.

Expected Behavior

ion-footer element should disappear completely when the sheet modal is dismissed

Steps to Reproduce

1. Open App in DevTools as mobile device. (screenshot)
2. Open a sheet modal
3. Scroll down within the modal with slight overscroll
4. Dismiss the modal
5. Observe that the ion-footer remains rendered on screen despite the modal being dismissed

Code Reproduction URL

https://stackblitz.com/edit/xj8qeuyy?file=src%2Fapp%2Fexample.component.html

Ionic Info

Ionic:

Ionic CLI : 7.2.1 (/usr/local/share/nvm/versions/node/v22.16.0/lib/node_modules/@ionic/cli)
Ionic Framework : @ionic/angular 8.6.0
@angular-devkit/build-angular : 19.2.14
@angular-devkit/schematics : 19.2.14
@angular/cli : 19.2.14
@ionic/angular-toolkit : 12.2.0

Capacitor:

Capacitor CLI : 7.3.0
@capacitor/android : not installed
@capacitor/core : 7.3.0
@capacitor/ios : not installed

Utility:

cordova-res : not installed globally
native-run : 2.0.1

System:

NodeJS : v22.16.0 (/usr/local/share/nvm/versions/node/v22.16.0/bin/node)
npm : 10.9.2
OS : Linux 5.15

Additional Information

• Related to issue: fix(sheet): move sheet footers instead of cloning while dragging #30433
• @ShaneK Could you please take a look at this issue?

[ShaneK]

I've verified this is a bug. The key steps to reproduction are it being a mobile view and needing to drag the scroll it with your mouse (using pointer events) until it's at the bottom. For some reason, the modal thinks it's moving during this time and doesn't trigger onFinish or anything and never unlocks itself.

[ShaneK]

@matejdurajka I have a PR up to address this, I'm hoping to get it out in the next patch. In the mean time, you can try out the solution with the dev build 8.6.1-dev.11749575087.1b86eb67

Edit: This will be fixed in 8.6.1, which I expect will deploy tomorrow

[ShaneK]

The fix for this has been released in 8.6.1, thanks for the report!