Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued #86

Closed
rniwa opened this issue Nov 5, 2019 · 4 comments

Comments

@rniwa
Copy link

rniwa commented Nov 5, 2019

https://w3c.github.io/requestidlecallback/#invoke-idle-callbacks-algorithm says

If the user-agent believes it should end the idle period early due to newly scheduled high-priority work, skip to step 4.

This should be defined in terms of any of the task sources in the HTML5 event loop having a task enqueued.

@rniwa rniwa changed the title 6.2. step 1 should be defined in terms of task sources having tasks enqueued 6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued Nov 5, 2019
rmcilroy added a commit to rmcilroy/requestidlecallback that referenced this issue Nov 14, 2019
rmcilroy added a commit to rmcilroy/requestidlecallback that referenced this issue Nov 14, 2019
@yoavweiss yoavweiss added this to the Level 1 milestone Nov 2, 2020
@noamr
Copy link
Contributor

noamr commented Oct 11, 2021

I think this is solved by #95 and whatwg/html#7166 once they are merged.

@noamr
Copy link
Contributor

noamr commented Nov 22, 2021

I believe this can be closed now that #95 is merged.

@yoavweiss
Copy link
Contributor

@rniwa - Any objections to closing this?

@noamr
Copy link
Contributor

noamr commented Jan 17, 2022

Closing. Feel free to reopen.

@noamr noamr closed this as completed Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants