javascript定时器使用(国外英语资料).docVIP

javascript定时器使用(国外英语资料) JavaScript thread explanation (setTimeout, setInterval, you dont know) JavaScripts setTimeout and setInterval are two easy ways to cheat other peoples feelings, because we often start thinking that calls are executed in a certain way, and I think a lot of people feel the same way, for example SetTimeout (function () {alert (Hello)?}, 0); SetInterval (callbackFunction, 100); As regards the setTimeout method is executed immediately, because it is not baseless but said, but the JavaScript API document defines second parameters for every few milliseconds after the callback method is executed. This is set to 0 msec, behoove were immediately executed. Similarly, the callbackFunction approach to setInterval is immediately implemented at 100 milliseconds intervals! But as the JavaScript application development experience continues to grow and enrich, one day youve found a weird piece of code thats puzzling: Div.onclick = function () { SetTimeout (function (), {document.getElementById (` inputField ),.Focus (),}, 0); }; Since it was 0 milliseconds after the execution, then what did setTimeout do with the moment, the firm belief has begun to waver Until the last day, you accidentally wrote a bad piece of code: SetTimeout (function) (while (true) {} {}, 100); SetTimeout (function () {alert (Hello)?}, 200); SetInterval (callbackFunction, 200); The first line of code into the dead cycle, but you will find that second soon, third is not a foregone conclusion, alert regards no, without hearing a word about callbacKFunction! When you are completely lost, it is difficult to accept, because the change of cognitive process established for a long time to accept new ideas is painful, but the real situation in front of JavaScript truth and will not stop because of the pain, lets start the JavaScript thread and timer discovery! Unplug the clouds and see the moon One of the main reasons for all of the above errors is that the subconscious thinks that the JavaScript