Ionic-framework: Changing detect stop works when handle a tab click event.

[netsesame2]

Ionic version: (check one with "x")
[ ] 1.x
[x] 2.x

I'm submitting a ... (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/

Your system information:

ordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.4
Ionic CLI Version: 2.1.18
Ionic App Lib Version: 2.1.9
Ionic App Scripts Version: 0.0.47
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v4.3.1
Xcode version: Not installed

Current behavior:

In an ionic's tabs based app, if we handle a button click from a tab button, change some states, ionic's changing detecting mechanism for the current page will stop working. Only thing we can do is exist and re-enter the view.

Expected behavior:

We hope it will be that, by clicking a tab button, change some states, the states will be updated in the binding views.

Steps to reproduce:

1. start a new project demo with default tabs template.
2. add a button tab in tabs.html as:

1. Inject events into tabs.ts, and add a test method in tabs.ts:

export class TabsPage {
...
constructor(private events: Events) {}

takePhoto() {
this.events.publish("data:changed");
}
}

1. Inject Events into home.ts, and subscribe to above event:

   export class HomePage {
   datatest: string = "old";

   constructor(public navCtrl: NavController, public events: Events) {
   events.subscribe("data:changed", this.change.bind(this));
   }

   change() {
   console.log("data changed!");
   this.datatest = "new!";
   }
   }

2. add a variable binding to anywhere in home.html:

TEST
{{datatest}}

1. click the 'camera‘ tab, watch the home page. no update is happen. while the console print the expected value.
2. click the 'test' button on home page, no update is happen also.
3. re-enter the home page, repeat 7, update take effect.

[mhartington]

Spook too soon. Looks like you're right. Thanks for the heads up

[matthewfreedman]

This looks like a duplicate of #9392. I am affected by the same issue.

[kelvindart]

I believe so - if so, then @manucorporat has fixed it I believe - see: #9512 (but the rc.5 milestone was removed from #9392, so I do not know if it is destined for rc.5 or not).

[mhartington]

Pulling down #9512 locally and applying it to my test seem to fix things!

[netsesame2]

So, where can I get this fix?

[mhartington]

We'll cut a nightly release with this soon. It will be officially available in the next release

On Jan 6, 2017, at 8:11 PM, netsesame [e-mail] wrote:

So, where can I get this fix?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

[brandyscarney]

This will be in the next release, if you'd like to test it sooner please install the latest nightly:

npm install --save ionic-angular@nightly

Let us know if you see any problems. Thanks!

[netsesame2]

The nightly version fix it perfectly. Thanks a lot.

[ionitron-bot[bot]]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.