|
|
|
|
|
|
by erinaceousjones
613 days ago
|
|
|
I think it's more likely that it's just "undefined behaviour" and up to the implementers of the JavaScript engines. Given that modern browsers do limit and throttle how much you can do with setTimeout in some situations (try to use setTimeout on a page after you've switched to a VR context! More than like 120hz and it'll just.... Not run the timeout anymore, from experience with Chrome). The browser devs have decided it's acceptable to change the behaviour of setTimeout in some situations. https://developer.chrome.com/blog/timer-throttling-in-chrome... |
|
|