feat(refresher): add ionPullStart and ionPullEnd events

[ShaneK]

Issue number: resolves #24524

---

What is the current behavior?

There is no way to know when the refresher has fully returned to its inactive state after a pull gesture. The existing ionStart event fires when pulling begins, but there is no corresponding end event. Watching the progress property is insufficient because hitting zero doesn’t necessarily mean the user has completed the pull gesture.

What is the new behavior?

Two new events are added to the refresher component:

• ionPullStart: Emitted when the user begins pulling down (same as ionStart, which is now deprecated)
• ionPullEnd: Emitted when the refresher returns to inactive state, with a reason property of 'complete' or 'cancel' indicating whether the refresh operation completed successfully or was cancelled

This allows you to know both when the user is no longer touching the screen AND when the refresher is ready to be pulled again.

Does this introduce a breaking change?

• Yes
• No

Other information

Test page:
https://ionic-framework-git-fw-6591-ionic1.vercel.app/src/components/refresher/test/basic/index.html

Current dev build:

8.7.17-dev.11770319814.172b4f50

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ionic-framework	Ready	Preview, Comment	Feb 5, 2026 7:43pm

[WhatsThatItsPat]

Thanks for the update. I look forward to playing with it.

I have something related on my mind.

On a page without a refresher, you can obviously still pull down and rubber band past the top (scrollY is less than 0). If you keep your figure on the screen and hold the content still in that rubber-banded state, isScrolling will change to false and ionScrollEnd will fire (I think), even though you're still in the middle of a scroll. When you continue the gesture or let go, it will go back to true until it animates to its normal resting place.

I think you should be still be considered scrolling when you're rubber banding / elastic scrolling, even if you manually pause the scroll. Only when ion-content comes to a rest AND your gesture is over should the ionScrollEnd fire.

Anyway, I haven't thought of that in a year+, but I'm pretty sure that's the issue. This one reminded me of it because of the start and end stuff.

Maybe I'll look at that again in my free time.