When imported, the following web-platform-tests time out:
html/webappapis/idle-callbacks/callback-idle-periods.html
html/webappapis/idle-callbacks/callback-timeout-with-raf.html
html/webappapis/idle-callbacks/basic.html
Oops, just noticed you weren't on here Ross. Didn't we determine that the non-virtual test harness didn't support idle callbacks or something like that?
Yes, the test harness uses the single-threaded compositor, which never initiates idle periods. We either need to fix that, or change the test harness to use the multi-threaded compositor. Thoughts Sami?
I think last time we concluded there isn't really anything stopping the single threaded compositor from running idle tasks. We just need someone to do it :)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by dtapu...@chromium.org
, Nov 21 2016