Skip to Content
Platform.Ontology

Task scheduling (postTask, yield)

Lets a page prioritize its own tasks and yield to input so it stays responsive.

Works without askingThings a page can doSchedulingWeb browsersWhile you use it

In one line

Can sort its own tasks so the page stays quick when you tap

Lets a page prioritize its own tasks and yield to input so it stays responsive.

A site can order its work and split long tasks. It cannot run when the tab is hidden any faster; it only improves smoothness inside the page.

What it can and can't do

What the user does: Nothing. It happens while the page runs and you scroll or tap.

It can

  • Run important page tasks before less important ones
  • Pause its own long work so taps and scrolls feel smooth
  • Cancel or move its own queued tasks

It cannot

  • Change what other tabs or other sites do
  • Speed up the device itself
  • Skip the browser's own power saving rules
  • Work in Safari or on iPhone, where it is not offered yet

How it differs between platforms: Chrome and Edge and Firefox support it. Safari, including on iPhone, does not yet.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported942021-09-21None
EdgeSupported942021-09-24None
FirefoxSupported1422025-08-19None
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported942021-09-21None
Samsung InternetSupported17.02022-05-04None

How a site asks for it

APIscheduler.postTask(fn, {priority}); scheduler.yield(); isInputPending()
Browser compat keysapi.Scheduler.postTask
api.Scheduler.yield
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
Activationnone
How long it lastsNone
How to take it backNothing to revoke (no permission is stored)
Inside an iframeNo iframe flag

Typical flow

  1. Call scheduler.postTask with a priority
  2. Browser runs it after higher priority work
  3. AbortController can cancel it

Data you get

Shape: none

No individual data fields. The signal is the access itself.

Technical limits

  • Priorities: user-blocking, user-visible, background
  • Does not bypass background tab throttling
  • Support per MDN BCD: Chrome 94 (postTask) and 129 (yield), Firefox 142, no Safari support

The story

What it is

A page can rank its own jobs so it stays responsive when you tap.

For you

You never see it. A page that uses it responds faster when you tap a button while it is still loading something else.

For makers

Makers use it to meet speed scores that affect search ranking and sales. Giving the browser room to handle taps first makes heavy pages feel quick.

Where you see it

TypeExampleApps
shoppingA busy product page loads reviews in the background so the Add to cart button answers right away.Amazon, Shopify stores
gamesA browser game keeps frames steady by deferring low priority work, like loading far away level pieces.None named
productivityA big web spreadsheet recalculates in small chunks so typing is not delayed.Google Sheets
analyticsMeasurement scripts are queued at low priority so they do not slow the page.Google Tag Manager
adsAds load at a lower priority than the article text.None named
socialA feed renders posts slice by slice as you scroll.X, Facebook

Risks

  • Few for readers
  • Unequal priority for ads

What the platform says

Good uses and abuse

Legitimate uses

  • INP and responsiveness work

Known abuse

  • None meaningful

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2021-09, Chrome 94: scheduler.postTask ships
  • 2024-09, Chrome 129: scheduler.yield ships
  • 2025-08, Firefox 142: Scheduler API ships

Sources

How well checked: Based on official documentation.

On this page