Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
bug: ion-segment (ionChange) trigger is not consistent on start #19204
ion-segment (ionChange) trigger is not consistent when opening multiple pages containing ion-segment.
Imagine 2 tab pages, named Tab2 and Tab3 for convenience, both with ion-segment. If you open the first one Tab2 the ionChange of the ion-segment is not triggered (as expected), if you afterwards (without restarting the app) open the Tab3 page its ionChange is fired (Unexpected).
This also works vice-versa. Restarting the app and opening first Tab3 will not fire the ionChange of the ion-segment, afterwards opening Tab2 will fire ionChange which is unexpected.
One would expect that all pages with ion-segment wouldn't fire its ionChange upon opening. Regardless of which page was opened first.
Steps to reproduce: