Re: [RequestIdleCallback] Editor's Draft of requestIdleCallback spec

We have landed an implementation of the requestIdleCallback API in Chrome
Canary, behind the "--enable-experimental-web-platform-features" flag.  It
is based on the most recent version of the spec, available at
https://w3c.github.io/requestidlecallback/.

To give it a go:
- Download Chrome Canary (version 46.0.2490.0 or above)
- Enable chrome://flags/#enable-experimental-web-platform-features
- Restart the browser
- The API should be accessible as window.requestIdleCallback()

Please give it a go and let us know if you have any feedback on either the
API spec or the implementation of the API in Chrome.

Cheers,
Ross

On 22 July 2015 at 16:58, Ross McIlroy <rmcilroy@google.com> wrote:

>
> Example 1 uses isExpired() which isn't defined anywhere.
>>
>
> Your right, this should have been isExceeded() which is defined in section
> 4. I've just pushed a change to correct this.
>
> Fig.1 uses [Input], Fig. 2 [Handle Input]. What is the difference between
>> those?
>
>
> Fig.1 shows the situation where the browser has just finished rendering
> the current frame, but knows it will need to render the next frame by the
> next VSync (e.g., because animations are running, or the page is being
> scrolled). Fig.2 shows the situation where the browser becomes idle (e.g.,
> finishes rendering the final frame of an animation) and doesn't have any
> more frames to render (e.g., the end of the idle period is unknown). Does
> this clarify things?
>
> Thanks for your comments!
>
>