3 ms·
The javascript spec requires a setinterval to block... Thats as intended. What isn't intended is that all kinds of management messages that involve the rende
by londons_explore 5y ago
The javascript spec requires a setinterval to block... Thats as intended.
What isn't intended is that all kinds of management messages that involve the renderer will block, like for example closing the tab, printing the page, spellchecking, adding to bookmarks, etc...
A few of those things Chrome works around with a nested event loop that only handles certain types of events, but it's very fragile and a big maintenance burden, so they want to get rid of it.