[TIMOB-1093] Android: setInterval continues after exiting the test
|Labels||android, defect, setinterval|
seems to continue to run (from console logging) after you exit from the test.
- Todd 2011-04-15
I found a potential issue with setInterval and setTimeout, though it may related or operating as designed the documentation does not mention this caveat on usage
In simple app.js
1. use setInterval(testFunc,100) 2. in the testFunction just use Ti.API.info('interval fire'); to verify operation 3. create a heavywieght window by setting navBarHidden:true property and then open it.
You should see that the timer fires until the heavywieght opens, remove the navBarHidden property and the event continues to fire even after the open.
Not sure if this is a context issue or what but seems like it should work both with heavywieght and non-heavywieght windows since app.js continues to execute other in line code just fine after the open.
- Ping Wang 2012-07-25 Cannot reproduce.
- Lee Morris 2017-03-03 Closing issue due to time passed and irrelevance of the ticket.