You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ever since the release of beta7 I has had a bug in the app I'm developing where the touch events were completely broken (i.e., not working, no buttons, no scroll, nothing.)
It happens when I switch between two states too fast. In my app, the first state is the login state. When the user is logged, he goes to a state where he has to select one item on a list, but if there's only one item, then I "redirect" him to the main page.
Something interesting is that playing with the setTimeout values it fixes it. If the timeout is too small or too big (for me 10ms and 1000ms) then it works. but 50-150ms it doesn't. It looks like it only happens when it's switching between states.
It didn't happen in beta6.
The text was updated successfully, but these errors were encountered:
@adamdbradley
Tested in Android 2.3.6 and it works! (it is fixed, at least, for this device)
I just checked it didn't work in beta9, but it does in beta10.
By now I can't test in any other devices, but if you need so just let me know and I will test it asap.
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.
Ever since the release of beta7 I has had a bug in the app I'm developing where the touch events were completely broken (i.e., not working, no buttons, no scroll, nothing.)
I managed to find when did it happen and made a plunker with the last nightly build: http://plnkr.co/edit/SVOuj4hqB8anIpMkgyu0?p=preview
It happens when I switch between two states too fast. In my app, the first state is the login state. When the user is logged, he goes to a state where he has to select one item on a list, but if there's only one item, then I "redirect" him to the main page.
Something interesting is that playing with the setTimeout values it fixes it. If the timeout is too small or too big (for me 10ms and 1000ms) then it works. but 50-150ms it doesn't. It looks like it only happens when it's switching between states.
It didn't happen in beta6.
The text was updated successfully, but these errors were encountered: