Hi,
On Tue, May 13, 2014 at 12:02 PM, Serban.Balamaci <thespamtr...@gmail.com>wrote: > Hi, > > Why so low of a timeout 50ms? > > https://github.com/reiern70/antilia-bits/blob/master/client-sign-out-parent/client-sign-out/src/main/java/com/antilia/signout/InactivitySignOutPanel.js#L34 > > should it not be something like 5000? I don't see the point of counting > down > so often. Maybe count down every 5 secs. Don't forget also to decrease the > counter accordingly > . > Yes, this was just an example on how this could be done. I'm not even using this myself... Probably that value should be a parameter passed via JAVA behavior. > I imagine also using console.log('time is now ...') when the timer > decreases > might provide some insights on what's exactly going on. > Well there is an onChange function you can pass and do there whatever you want... e.g. log into the console. > > I'd be mad as an user that something it's eating up my cpu if you'd do that > and be thankful for things like: > > https://stackoverflow.com/questions/6032429/chrome-timeouts-interval-suspended-in-background-tabs > > > Thanks for the pointer... you spare me typing for this on google. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Ajax-timer-not-counting-when-tab-doesn-t-have-focus-tp4665789p4665802.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
