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

Editorial: Use the HTML spec's timers infrastructure for timeout #98

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from

Conversation

andreubotella
Copy link
Member

@andreubotella andreubotella commented Dec 2, 2021

In whatwg/html#7349, the HTML spec factored out part of the infrastructure for setTimeout() into a "run steps after a timeout" algorithm for use by other specs. This change updates requestIdleCallback() to use that algorithm when the timeout property is present and positive.


Preview | Diff

In whatwg/html#7349, the HTML spec factored out part of the
infrastructure for `setTimeout()` into a "run steps after a timeout"
algorithm for use by other specs. This change updates
`requestIdleCallback()` to use that algorithm when the `timeout`
property is present and positive.
@w3cbot
Copy link

w3cbot commented Dec 2, 2021

andreubotella marked as non substantive for IPR from ash-nazg.

Copy link
Contributor

@yoavweiss yoavweiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for aligning this with HTML spec changes.

@noamr - can you review?

index.html Show resolved Hide resolved
@andreubotella
Copy link
Member Author

andreubotella commented Dec 2, 2021

Come to think about it, this change is not in fact editorial, since the "run steps after a timeout" algorithm adds an entry to the map of active timers, which in turn affects the idle deadline. It might still be worth making the change, though.

Copy link
Contributor

@noamr noamr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yoavweiss
Copy link
Contributor

@andreubotella - For some reason, we never clicked the green button and merged this.. Any reason I shouldn't? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants