setTimeout is a well established and mature API. This change poses a risk of breaking websites and tests that rely on the current clamping behavior and the subtle task ordering that it entails. As an example, this change breaks the assumption that setTimeout(0) causes micro tasks to run in at least one case in Chrome tests (crbug.com/1302309). On the flip side, the implementation in Chrome is already non compliant (crbug.com/1108877). There's also a similar experiment on beta that is ongoing (crbug.com/1263190). Devs can use chrome://flags#unthrottled-nested-timeout to test their sites for compatibility issues.
setTimeout() and setInterval() have an associated trace event in DevTools. https://developer.chrome.com/docs/devtools/evaluate-performance/performance-reference/
|DevTrial on desktop||101|
|DevTrial on android||101|
I don't know maybe just need some incentive tired of the short end of the stick I mean all the time and effort u guys put u can't do it
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADnb78jSSZuZTNnQ1me83xUD7XO82PKS4btmPKBGCkkqukxh_Q%40mail.gmail.com.