Odd JavaScript Bug

From:	Ally	22 Sep 2006 17:52
To:	Peter (BOUGHTONP)	4 of 6

30698.4 In reply to 30698.1

quote:

The setTimeout(...,0) just means execute immediately. In this form, everything works fine.

Not putting it in a SetTimeout would do exactly the same thing?

And I've not seen the other thread, but try:

code:

setTimeout(eval("alert(elem('total_cost').innerText)"),0);

or

code:

setTimeout(new function() {alert(elem('total_cost').innerText)},0);

0/0

More

From:	Matt	22 Sep 2006 18:20
To:	Ally	5 of 6

30698.5 In reply to 30698.4
code: Not putting it in a SetTimeout would do exactly the same thing? It's not. By calling a function with SetTimeout you don't interrupt the code flow following the call which means you can pretty much have have two functions running at the same time. It's like a half-arsed attempt at threading except it's not because Javascript doesn't do threading.

0/0

More

From:	Peter (BOUGHTONP)	22 Sep 2006 18:27
To:	Ally	6 of 6

30698.6 In reply to 30698.4
Well, what Matt says is right, but yeah it works without the setTimeout just like with it at 0. It's working consistantly now though (with a 50ms setTimeout on the calling function instead), so it possibly might have been a JS caching issue earlier. `3.1415P265E589T932E846R64338`

0/0

More