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.

Sign up for GitHub

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

Jump to bottom

Fix typos #36109

Merged
merged 3 commits into from
Sep 30, 2024
Merged

Fix typos #36109

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
428cff8
Fix typos
OnkarRuikar Sep 30, 2024
59bca20
add remainging to ignore list
OnkarRuikar Sep 30, 2024
227862f
run cspell formatter
OnkarRuikar Sep 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .vscode/ignore-list.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -649,6 +649,7 @@ camelcase
Camen
Camino
Camtasia
canadien
cand
Candara
Caniuse
Expand Down Expand Up @@ -2979,6 +2980,7 @@ monkeypatch
monoscopic
Montag
montecarlo
Montulli
moof
Moonrocks
Mooog
Expand Down Expand Up @@ -3311,6 +3313,7 @@ nonliteral
nono
nonsparse
nonstrict
nonterminal
nonummy
nonumy
Norah
Expand Down
2 changes: 1 addition & 1 deletion files/en-us/web/api/scheduler/yield/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ The order in which the promise returned by `scheduler.yield()` is resolved relat

By default, `scheduler.yield()` is run with a [`"user-visible"`](/en-US/docs/Web/API/Prioritized_Task_Scheduling_API#user-visible) priority. However, continuation after a `scheduler.yield()` call has a slightly different behavior than `scheduler.postTask()` tasks of the same `priority`.

`scheduler.yield()` enqueues its task in a boosted task queue compared to a `scheduler.postTask()` of the same prioritiy level. So, for instance, a `scheduler.yield()` continuation with `"user-visible"` priority will be prioritized after `scheduler.postTask()` tasks of the higher `"user-blocking"` priority level, but before `scheduler.postTask()` tasks of the same `"user-visible"` priority (in the spec, this is defined by a task queue's [effective priority](https://wicg.github.io/scheduling-apis/#scheduler-task-queue-effective-priority)).
`scheduler.yield()` enqueues its task in a boosted task queue compared to a `scheduler.postTask()` of the same priority level. So, for instance, a `scheduler.yield()` continuation with `"user-visible"` priority will be prioritized after `scheduler.postTask()` tasks of the higher `"user-blocking"` priority level, but before `scheduler.postTask()` tasks of the same `"user-visible"` priority (in the spec, this is defined by a task queue's [effective priority](https://wicg.github.io/scheduling-apis/#scheduler-task-queue-effective-priority)).

This is sometimes described as `scheduler.yield()` enqueuing its task at the front of a priority level's queue, while `scheduler.postTask()` tasks go at the end. This can be a useful mental model. In situations with just a few tasks, this means that with the same priority, the `scheduler.yield()` continuation will come first, allowing additional flexibility in how tasks can be scheduled. For example:

Expand Down