Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.12.2 breaks transition behaviour #13

Open
jorjordandan opened this issue Aug 20, 2015 · 4 comments
Open

1.12.2 breaks transition behaviour #13

jorjordandan opened this issue Aug 20, 2015 · 4 comments

Comments

@jorjordandan
Copy link

If you clone/download the meteoric demo app that with all the components, and use it with useraccounts:ionic 1.12.2 , after you select the useraccounts tab, the slider slides half way, stops, and then jerks across... but if you use 1.12.0 there is no issue.
This behaviour was present on chrome and safari.
I'm not familiar enough with this repo to possibly suggest what the cause is, I looked through the last couple commits and didn't see the issue.... I'll keep checking but I'm pretty new to ionic

EDIT: 1.12.1 also fine.. gotta be something to do with that new onRendered callback, I guess...

@jorjordandan
Copy link
Author

Okay, I spoke too soon when I said there is no issue - with 1.12.1 there is an error in the console:

Exception from Tracker afterFlush function:
 debug.js:41 TypeError: callbacks[i].call is not a function
     at template.js:116
     at Function.Template._withTemplateInstanceFunc (template.js:437)
     at fireCallbacks (template.js:112)
     at null.<anonymous> (template.js:205)
     at view.js:104
     at Object.Blaze._withCurrentView (view.js:523)
     at view.js:103

but the transition works smoothy, and the authentication still works fine. So I'll stick with 12.1.1 for now...

@FreefallGeek
Copy link

@jorjordandan were you able to resolve this issue? I'm having the same problem with the useraccounts:materialize package. When I remove the {{>atForm}} template, this console error goes away. As soon as I re-add it to my template flow, it generates this console error again, so I'm relatively certain that its the useraccounts package that is causing the error.

@jorjordandan
Copy link
Author

There's more of a discussion about what happened for me here. I still don't know what the issue was, but I think that perhaps you need to make sure you have the latest version of useraccounts:core

@splendido
Copy link
Member

any news on this?
Whas it a problem with the packages' version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants