Scheduling: setTimeout and setInterval #3423
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shallow-beach
suggested changes
Aug 24, 2024
| @@ -127,7 +127,7 @@ setTimeout(() => { clearInterval(timerId); alert('stop'); }, 5000); | |||
| ``` | |||
|
|
|||
| ```smart header="Time goes on while `alert` is shown" | |||
| In most browsers, including Chrome and Firefox the internal timer continues "ticking" while showing `alert/confirm/prompt`. | |||
| In most browsers including Chrome and Firefox, the internal timer continues "ticking" while showing `alert/confirm/prompt`. | |||
There was a problem hiding this comment.
IMO should have both:
In most browsers, including Chrome and Firefox, the internal timer continues "ticking" while showing
alert/confirm/prompt.
| @@ -208,7 +208,7 @@ Did you notice? | |||
|
|
|||
| That's normal, because the time taken by `func`'s execution "consumes" a part of the interval. | |||
|
|
|||
| It is possible that `func`'s execution turns out to be longer than we expected and takes more than 100ms. | |||
| It is possible that `func`'s execution to be longer than we expected and take more than 100ms. | |||
There was a problem hiding this comment.
disagree, leave as original
| @@ -256,9 +256,9 @@ The first line "puts the call into calendar after 0ms". But the scheduler will o | |||
| There are also advanced browser-related use cases of zero-delay timeout, that we'll discuss in the chapter <info:event-loop>. | |||
|
|
|||
| ````smart header="Zero delay is in fact not zero (in a browser)" | |||
| In the browser, there's a limitation of how often nested timers can run. The [HTML Living Standard](https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timers) says: "after five nested timers, the interval is forced to be at least 4 milliseconds.". | |||
| In the browser, there's a limitation for how often nested timers can run. The [HTML Living Standard](https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timers) says: "after five nested timers, the interval is forced to be at least 4 milliseconds.". | |||
javascript-translate-bot
added
the
changes requested
|
Please make the requested changes. After it, add a comment "/done". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
lines 101, 211, 259, 261, 280, 282 and 284 - improvement suggestions
line 130 - grammar fix