← Back to release summary

Pause Worklets and Dedicated Workers Execution on document freeze

Category

Performance

Type

New or changed feature

Status

In developer trial (Behind a flag) (Chrome 76)

Intent stage

Start prototyping

• Breaking change: No
• Enterprise impact: None
• Spec maturity: Incubation
• Web Platform Tests: Yes

WPT details: https://wpt.fyi/results/lifecycle/worker-dispay-none.tentative.html?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned

Summary

Dedicated workers and worklets continue to execute even though documents may be frozen due to the page lifecycle.

Motivation

All threads in a frozen document should be frozen.

Standards & signals

• Specification: https://wicg.github.io/page-lifecycle/spec.html
• Firefox: No signal — Firefox does this for workers going into bfcache.
• Safari: No signal
• Web developers: No signals
• Tracking bug: https://crbug.com/957589

Ecosystem

• Web Platform Tests: https://wpt.fyi/results/?q=lifecycle%2Fworker-dispay-none
• Chrome Platform Showcase: https://chrome-platform-showcase.paulkinlan-ea.deno.net/features
• GenDN reference: https://gendn.paulkinlan-ea.deno.net/features
• chrome.dev demos search: https://www.google.com/search?q=site%3Achrome.dev+Pause%20Worklets%20and%20Dedicated%20Workers%20Execution%20on%20document%20freeze
• MDN Web Docs: https://developer.mozilla.org/en-US/search?q=Pause%20Worklets%20and%20Dedicated%20Workers%20Execution%20on%20document%20freeze
• Baseline status: https://webstatus.dev/?q=Pause%20Worklets%20and%20Dedicated%20Workers%20Execution%20on%20document%20freeze

Docs: https://github.com/WICG/page-lifecycle/pull/35

Explainers: https://github.com/WICG/page-lifecycle/pull/35

View on chromestatus.com