Exactly because it's single threaded and with an event loop is practically impossible to set two timers with the same delay to trigger at the same time: one will always trigger before the other.
Keep in mind that setInterval does not exactly say: "hey, run this function exactly every x milliseconds at all costs" but it says "hey, put this function to be executed in the queue every x milliseconds" which is a subtle difference.
If the browser is processing other events when the clock fires than the setInterval will be delayed and it can also be dropped if there's another timer scheduled for execution in that exact instant or they can fire without respecting the interval.
It will execute both but how... that it depends.
Exactly because it's single threaded and with an event loop is practically impossible to set two timers with the same delay to trigger at the same time: one will always trigger before the other.
Keep in mind that
setIntervaldoes not exactly say: "hey, run this function exactly every x milliseconds at all costs" but it says "hey, put this function to be executed in the queue every x milliseconds" which is a subtle difference.If the browser is processing other events when the clock fires than the
setIntervalwill be delayed and it can also be dropped if there's another timer scheduled for execution in that exact instant or they can fire without respecting the interval.A really good explanation by John Resig: johnresig.com/blog/how-javascript-...