bug: <ion-segment> @ionChange no longer fires since 8.4.3 ionic-vue update

[jacobg]

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

In ionic-vue 8.4.2, @ionChange would fire when clicking on each ionic-segment-button. Since 8.4.3, @ionChange no longer fires.

Expected Behavior

@ionChange should fire.

Steps to Reproduce

See instructions above.

Code Reproduction URL

https://ionicframework.com/docs/api/segment#events

Ionic Info

Ionic:

Ionic CLI : 7.2.0

Utility:

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

System:

NodeJS : v18.16.0
npm : 9.5.1
OS : macOS Unknown

Additional Information

No response

[Alex0x47]

I'm having the same issue with @ionChange not being fired but on ion-toggle components, after upgrading to 8.4.3. Reverted to 8.4.2 and it's working.

[flroent]

Same thing here, @ionChange not fired on ion-segment, @ionInput not fired on ion-input and ion-searchbar

[DanielNunees]

Same issue, neither @ionInput or @ionChange are firing.

I reverted to v8.1.1, probably don't need to go back that far, but this version has no issues.

[MarvinRucinski]

Same here, going back to 8.4.2 fixes this.

[kyaustad]

having same issue. Setting to 8.4.2 fixed for me as well. none of the Ion specific events seemed to be firing for me on most components like toggles and searchbars but the revert seemed to fix things

[jacobg]

Is this an issue only on Ionic Vue, or does Ionic React also have this issue?

[kensodemann]

@jacobg : I am working on updating several demo apps and have only be affected by this in the Vue based one. Angular and React do not appear to be affected at all.

[jacobg]

@kensodemann Thanks. I'm afraid we may hear an announcement next week that only the React implementation will be maintained moving forward and the others will be dropped, as only React is needed for the maintainer's commercial business model. That would explain why there is this breaking bug in the most recent release for Vue, and yet there is no response or fix for it.

[dolthead]

@kensodemann Thanks. I'm afraid we may hear an announcement next week that only the React implementation will be maintained moving forward and the others will be dropped, as only React is needed for the maintainer's commercial business model. That would explain why there is this breaking bug in the most recent release for Vue, and yet there is no response or fix for it.

All indications point to this being fixed and pushed out within a week or two. And Vue, Angular and React will all continue to be supported. As mentioned, the temporary workaround is to downgrade to 8.4.2.

[IIxauII]

dynamic value assigning on ion-segment in ionic/angular afaik also broken

[roger-hermasch]

This might be obvious but we just wasted an hour figuring out that the caret (^) in our package.json led to a faulty version. FIXING it to 8.4.2 (no caret a the beginning!) fixed it for us as well - strongly hoping for a fix from ionic soon.