Hi, I'm reaching out to hear your feedback and interest for the requestIdleCallback API [0], [1].
Since the Blink intent to implement, we've been observing a high level of interest from the developer community (see comments on Paul Lewis's article [2], and reactions on twitter[3]). We would be curious to know if you have any concerns or suggestions for us to consider before moving further. Also, getting a sense of your interest in this API would be really useful. Thanks in advance! Note: Chrome 46 has a working implementation behind the experimental web platform features flag. [0]: Background (from Paul's article) "Many sites and apps have a lot of scripts to execute. Your JavaScript often needs to be run as soon as possible, but at the same time you don’t want it to get in the user’s way. If you send analytics data when the user is scrolling the page, or you append elements to the DOM while they happen to be tapping on the button, your web app can become unresponsive, resulting in a poor user experience. The good news is that there’s now an API that can help: requestIdleCallback. In the same way that adopting requestAnimationFrame allowed us to schedule animations properly and maximize our chances of hitting 60fps, requestIdleCallback will schedule work when there is free time at the end of a frame, or when the user is inactive." [1] https://w3c.github.io/requestidlecallback/ (a FPWD is in the queue) [2] https://developers.google.com/web/updates/2015/08/27/using-requestidlecallback?hl=en [3] https://twitter.com/search?q=requestIdleCallback&src=typd
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
