feat: swipe-to-close should support `e.detail.snapBreakpoint`

[aeharding]

Prerequisites

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

Describe the Feature Request

Sheet modals support the new snapBreakpoint parameter. It would be great if swipe-to-close dialogs also supported this parameter, so we could know if the dialog intends to continue animating to dismiss or not.

Describe the Use Case

Dismiss the keyboard when the user lifts their finger during a gesture, if the dialog will animate to dismissal.

Describe Preferred Solution

e.detail.snapBreakpoint (would just be 1 or 0) or something like that on ionDragEnd

Describe Alternatives

No response

Related Code

No response

Additional Information

No response

[thetaPC]

Thank you for the feature request!

Can you elaborate on why progress is not possible to be used? snapBreakpoint is meant for sheet modals as those have breakpoints. The more information that we can get then the better we can understand to provide a good solution.

[aeharding]

Hi @thetaPC!

The idea is, when you lift your finger on a swipe down, the modal can either:

1. Not dismiss (you didn't swipe far enough nor with enough momentum), or
2. Dismiss (you swiped far enough and/or with enough momentum)

progress just exposes the absolute amount that the dialog has closed, but does not expose information on where the dialog intends to animate to (either closing or remaining open).

You can see usage here in Voyager: aeharding/voyager#2227

Basically, if you swipe down I can start closing the keyboard at the moment you lift your finger from the screen, because snapBreakpoint would expose where Ionic intends to animate the dialog to (closing or remaining open)

[thetaPC]

@aeharding Thanks again for the feature request!

The team discussed this internally, and we agree that this would be a great addition to the framework.

Regarding the timeline, we have officially shifted our focus toward the future. As mentioned in the Ionic Framework 8.8 announcement, v8.8 marks the final minor release for the Ionic 8 lifecycle.

Because of this, we are no longer merging new features into v8. To ensure this is considered for the next major evolution of the framework, could you please change the base of your PR to the major-9.0 branch (instead of main)?

Once the base is updated, it will be in the right place for the team to take a look as we continue planning for Ionic 9.

[aeharding]

No prob :) done