Compute Pressure Level 1

W3C Working Draft

More details about this document
This version:
https://www.w3.org/TR/2023/WD-compute-pressure-20230328/
Latest published version:
https://www.w3.org/TR/compute-pressure/
Latest editor's draft:
https://w3c.github.io/compute-pressure/
History:
https://www.w3.org/standards/history/compute-pressure
Commit history
Test suite:
https://github.com/web-platform-tests/wpt/labels/compute-pressure
Editors:
Kenneth Rohde Christiansen (Intel Corporation)
Arnaud Mandy (Intel Corporation)
Former editors:
Olivier Yiptong (Google Inc.)
Victor Costan (Google Inc.)
Feedback:
GitHub w3c/compute-pressure (pull requests, new issue, open issues)

Abstract

The Compute Pressure API provides a way for websites to react to changes in the CPU pressure of the target device, such that websites can trade off resources for an improved user experience.

Status of This Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document was published by the Devices and Sensors Working Group as a Working Draft using the Recommendation track.

Publication as a Working Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 2 November 2021 W3C Process Document.

1. Introduction

This section is non-normative.

Modern applications often need to balance the trade offs and advantages of fully utilizing the system's computing resources, in order to provide a modern and delightful user experience.

As an example, many applications can render video effects with varying degrees of sophistication. These applications aim to provide the best user experience, while avoiding driving the user's device into a high pressure regime.

Utilization of processing units close to and often reaching 100% can lead to a bad user experience, as different tasks are fighting for the processing time. This can lead to slowless, which is especially noticeable with input delay. Further, a prolonged utilization close 100% can cause the processing units to heat up due to prolonged boosting, which can lead to throttling, resulting in an even worse user experience.

As a result of thermal limits, many smartphones, tablets and laptops can become uncomfortably hot to the touch. The fans in laptops and desktops can become so loud that they disrupt conversations or the users’ ability to focus.

In many cases, a device under high pressure appears to be unresponsive, as the operating system may fail to schedule the threads advancing the task that the user is waiting for. See also Use Cases.

2. A Note on Feature Detection

This section is non-normative.

Feature detection is an established web development best practice. Resources on the topic are plentiful on- and offline and the purpose of this section is not to discuss it further, but rather to put it in the context of detecting hardware-dependent features.

Consider the below feature detection examples:

Note

3. Concepts

This specification defines the following concepts:

3.1 Processing Units

Computing devices consist of a multitude of different processing units such as the Central Processing Unit (CPU), the Graphics Processing Unit (GPU) and many specialized processing units. The latter are becoming popular such as ones designed to accelerate specific tasks like machine learning or computer vision.

3.2 Supported sources

The specification currently defines the supported source types as global system thermals and the central processing unit, also know as the CPU. Future levels of this specification MAY introduce additional source types.

WebIDLenum PressureSource { "thermals", "cpu" };

The PressureSource enum represents the supported source types:

Note

3.3 Sampling and Reporting Rate

The sampling rate for a platform collector is defined as a rate at which the user agent obtains telemetry readings from the underlying platform, and it might differ from the pressure observers' requested sampling rates.

The reporting rate for a pressure observer is the rate at which it runs the data delivery steps.

The sampling rate differs from the requested sampling rate when the requested sampling rate exceeds upper or lower sampling rate bounds supported or accepted by the underlying platform and user agent.

It is recommended that the user agent limits the reporting rate as outlined in 11.1.1 Rate-limiting change notifications.

In case the user didn't request a sampling rate, the sampling rate is implementation-defined.

Note

4. Platform primitives

The platform collector refers to a platform interface, with which the user agent interacts to obtain the telemetry readings required by this specification.

A platform collector can be defined by the underlying platform (e.g. in a native telemetry framework) or by the user agent, if it has a direct access to hardware counters.

A platform collector can support telemetry for different source types of computing devices defined by PressureSource, or there can be multiple platform collectors.

From the implementation perspective platform collector can be treated as a software proxy for the corresponding hardware counters. It is possible to have multiple platform collector simultaneously interacting with the same underlying hardware if the underlying platform supports it.

In simple cases, a platform collector represents individual hardware counters, but if the provided counter readings are a product of data fusion performed in software, the platform collector represents the results of the data fusion process. This may happen in user space or in kernel space.

As collecting telemetry data often means polling hardware counters, it is not a free operation and thus, it should not happen if there are no one observing the data. See 10.5 Life-cycle and garbage collection for more information.

A platform collector samples data at a specific rate. A user agent may modify this rate (if possible) for privacy reasons, or ignore and fuse certain readings.

5. User notifications

It is RECOMMENDED that a user agent show some form of unobtrusive notification that informs the user when a pressure observer is active, as well as provides the user with the means to block the ongoing operation, or simply dismiss the notification.

6. Policy control

The Compute Pressure API defines a policy-controlled feature identified by the token "compute-pressure". Its default allowlist is ["self"].

Note

7. Internal Slot Definitions

Each global object has:

A registered observer consists of an observer (a PressureObserver object).

A constructed PressureObserver object has the following internal slots:

The user agent additionally has a max queued records integer, which is set to an implementation-defined value, greater than 0.

8. Pressure States

Pressure states represents the minimal set of useful states that allows websites to react to changes in compute and system pressure with minimal degration in quality or service, or user experience.

WebIDLenum PressureState { "nominal", "fair", "serious", "critical" };

The PressureState enum represents the pressure state with the following states:

9. Contributing Factors

Contributing factors represents the factors contributing to the system performance and current pressure state. In case the pressure state is nominal or fair, the PressureRecord internal slot [[Factors]] will always be empty.

Note
WebIDLenum PressureFactor { "thermal", "power-supply" };

The PressureFactor enum represents the contributing factors:

The change in contributing factors is substantial steps are as follows:

  1. If implementation-defined low-level hardware metrics that contribute to the system performance and current pressure state drop below or exceed an implementation-defined threshold for the current pressure state, return true.
  2. Return false.
Note

10. Pressure Observer

The Compute Pressure API enables developers to understand the pressure of system resources such as the CPU.

10.1 The PressureUpdateCallback callback

WebIDLcallback PressureUpdateCallback = undefined (
  sequence<PressureRecord> changes,
  PressureObserver observer
);
This callback will be invoked when the pressure state changes.

10.2 The PressureObserver object

The PressureObserver can be used to observe changes in the pressure states.

WebIDL[Exposed=(DedicatedWorker,SharedWorker,Window), SecureContext]
interface PressureObserver {
  constructor(PressureUpdateCallback callback, optional PressureObserverOptions options = {});

  Promise<undefined> observe(PressureSource source);
  undefined unobserve(PressureSource source);
  undefined disconnect();
  sequence<PressureRecord> takeRecords();

  [SameObject] static readonly attribute FrozenArray<PressureSource> supportedSources;
};

The PressureObserver interface represents a PressureObserver.

10.2.1 The constructor() method

The new PressureObserver(callback, options) constructor steps are:

  1. Set this.[[Callback]] to callback.
  2. If options["sampleRate"] is less than or equal to 0, throw a RangeError.
  3. Set this.[[SampleRate]] to options["sampleRate"].

10.2.2 The observe() method

The observe(source) method steps are:

  1. Let document be this's relevant settings object's associated Document.
  2. If document is not null and is not allowed to use the policy-controlled feature token "compute-pressure", return a promise rejected with NotAllowedError.
  3. Let promise be a new promise.
  4. Let pendingPromiseTuple be (source, promise).
  5. Append pendingPromiseTuple to this.[[PendingObservePromises]].
  6. React to promise:
  7. Run the following steps in parallel:
    1. If source is not a supported source type, queue a global task on the PressureObserver task source given document's relevant global object relevantGlobal to reject promise NotSupportedError and abort these steps.
    2. Activate data delivery of source data to relevantGlobal.
    3. Queue a global task on the PressureObserver task source given document's relevant global object relevantGlobal to run these steps:
      1. If promise was rejected, run the following substeps:
        1. If relevantGlobal's registered observer list for source is empty, deactivate data delivery of source data to relevantGlobal.
        2. Return.
      2. Append a new registered observer whose observer is this to relevantGlobal's registered observer list for source.
      3. Resolve promise.
  8. Return promise.

10.2.3 The unobserve() method

The unobserve(source) method steps are:

  1. If source is not a supported source type, throw "NotSupportedError".
  2. Remove from this.[[QueuedRecords]] all records associated with source.
  3. Remove this.[[LastRecordMap]][source].
  4. For each (promiseSource, pendingPromise) of this.[[PendingObservePromises]], if source is equal to promiseSource, reject pendingPromise with an AbortError.
  5. Let relevantGlobal be this's relevant global object.
  6. Remove any registered observer from relevantGlobal's registered observer list for source for which this is the registered observer.
  7. If the above registered observer list is empty, deactivate data delivery of source data to relevantGlobal.

10.2.4 The disconnect() method

The disconnect() method steps are:

  1. Empty observer.[[QueuedRecords]].
  2. Clear this.[[LastRecordMap]].
  3. For each (promiseSource, pendingPromise) of this.[[PendingObservePromises]], reject pendingPromise with an AbortError.
  4. Let relevantGlobal be this's relevant global object.
  5. Remove any registered observer from relevantGlobal's' registered observer list for all supported source types for which this is the observer.
  6. If the above registered observer list is empty, deactivate data delivery of source data to relevantGlobal.

10.2.5 The takeRecords() method

Note

The takeRecords() method steps are:

  1. Let records be a clone of observer.[[QueuedRecords]].
  2. Empty observer.[[QueuedRecords]].
  3. Return records.

10.2.6 The supportedSources attribute

The supportedSources attribute is informing on the supported source type by the platform collector.

The supportedSources getter steps are:

  1. Let sources be a list of source.
  2. Return observer's frozen array of supported source types.

Note

10.3 The PressureRecord interface

WebIDL[Exposed=(DedicatedWorker,SharedWorker,Window), SecureContext]
interface PressureRecord {
  readonly attribute PressureSource source;
  readonly attribute PressureState state;
  readonly attribute FrozenArray<PressureFactor> factors;
  readonly attribute DOMHighResTimeStamp time;
  [Default] object toJSON();
};

A constructed PressureRecord object has the following internal slots:

10.3.1 The source attribute

The source getter steps are to return its [[Source]] internal slot.

10.3.2 The state attribute

The state getter steps are to return its [[State]] internal slot.

10.3.3 The factors attribute

The factors getter steps are to return its [[Factors]] internal slot.

10.3.4 The time attribute

The time getter steps are to return its [[Time]] internal slot.

10.3.5 The toJSON member

When PressureRecord.toJSON is called, run Web IDL Standard's default toJSON steps.

10.4 The PressureObserverOptions dictionary

WebIDLdictionary PressureObserverOptions {
  double sampleRate = 1.0;
};

10.4.1 The sampleRate member

The sampleRate member represents the requested sampling rate expressed in Hz, ie. it represents the number of samples requested to be obtained from the hardware per second. The reporting rate will never exceed the requested sampling rate.

Note

10.5 Life-cycle and garbage collection

Each global object has a strong reference to registered observers in their registered observer list (one per source).

Note

10.6 Processing Model

This section outlines the steps the user agent must take when implementing the specification.

10.6.1 Supporting algorithms

Note
The passes privacy test steps given the argument observer and its relevant global object relevantGlobal, are as follows:
Note
The passes rate test steps given the argument observer, source and timestamp, are as follows:
  1. If observer.[[LastRecordMap]][source] does not exist, return true.
  2. Let record be observer.[[LastRecordMap]][source].
  3. Let sampleRate be observer.[[SampleRate]].
  4. Let timeDeltaMilliseconds = timestamp - record.[[Time]].
  5. Let intervalSeconds = 1 / sampleRate.
  6. If (timeDeltaMilliseconds / 1000) ≥ intervalSeconds, return true, otherwise return false.
The has change in data steps given the argument observer, source, state and factors, are as follows:
  1. If observer.[[LastRecordMap]][source] does not exist, return true.
  2. Let record be observer.[[LastRecordMap]][source].
  3. If record.[[State]] is not equal to state and change in contributing factors is substantial returns true, return true.
  4. If record.[[Factors]] and factors are not supersets of each other, return true.
  5. Return false.

10.6.2 Data delivery

Data delivery from a platform collector can be activate and deactivated in an implementation-defined manner per source type and global object.

Note

The data delivery steps that are run when an implementation-defined data sample of source type source is obtained from global object relevantGlobal's platform collector, are as follows:

  1. Let source be the source type of the data sample.
  2. Let state be an implementation-defined state given data and source.
  3. Let factors be an implementation-defined ordered set given data and source, potentially empty.
  4. Let timestamp be a timestamp representing the time the data was obtained from the relevantGlobal's platform collector.
    Note
  5. For each observer in relevantGlobal's registered observer list for source:
    1. If running passes privacy test with observer returns false, continue.
    2. If running passes rate test with observer, source and timestamp returns false, continue.
    3. If running has change in data with observer, source, state and factors returns false, continue.
    4. Run queue a record with observer, source, state, factors and timestamp.

10.6.3 Queue a PressureRecord

To queue a record given the arguments observer, source, state, factors and timestamp, run these steps:

  1. Let record be a new PressureRecord object with its [[Source]] set to source, [[State]] set to state, [[Factors]] set to factors and [[Time]] set to timestamp.
  2. If size of observer.[[QueuedRecords]] is greater than max queued records, then remove the first item.
  3. Append record to observer.[[QueuedRecords]].
  4. Set observer.[[LastRecordMap]][source] to record.
  5. Queue a pressure observer task with observer's relevant global object.

10.6.4 Queue a Pressure Observer Task

The PressureObserver task source is a task source used for scheduling tasks to 10.6.5 Notify Pressure Observers.

To queue a pressure observer task given relevantGlobal as input, run these steps:

  1. If the relevantGlobal's pressure observer task queued is true, then return.
  2. Set the relevantGlobal's pressure observer task queued to true.
  3. Queue a global task on PressureObserver task source with relevantGlobal to notify pressure observers.

10.6.5 Notify Pressure Observers

To notify pressure observers given relevantGlobal as input, run these steps:

  1. Set relevantGlobal's pressure observer task queued to false.
  2. Let notifySet be a new set of all observers in relevantGlobal’s registered observer lists.
  3. For each observer of notifySet:
    1. Let records be a clone of observer.[[QueuedRecords]].
    2. Empty observer.[[QueuedRecords]].
    3. If records is not empty, then invoke observer.[[Callback]] with records and observer. If this throws an exception, catch it, and report the exception.

10.6.6 Handling change of fully active

When a Document document is no longer fully active, deactivate data delivery of data of all supported source types to document's relevant global object.

When a worker with associated WorkerGlobalScope relevantGlobal is no longer an active needed workers, deactivate data delivery of data of all supported source types to relevantGlobal.

When a Document document becomes fully active, for each non-empty registered observer list associated the source type source, activate data delivery of source data to document's relevant global object.

When a worker with associated WorkerGlobalScope relevantGlobal becomes an active needed workers, for each non-empty registered observer list associated the source type source, activate data delivery of source data to document's relevant global object.

Note

10.6.7 Handle unloading document and closing of workers

When a worker with associated WorkerGlobalScope relevantGlobal, once relevantGlobal's closing flag is set to true, deactivate data delivery for all supported source types to relevantGlobal.

As one of the unloading document cleanup steps given Document document, deactivate data delivery for all supported source types to document's relevant global object.

11. Security and privacy considerations

Please consult the Security and Privacy Self-Assessment based upon the [security-privacy-questionnaire].

11.1 Minimizing information exposure

Exposing hardware related events related to low -level details such as exact CPU utilization or frequency increases the risk of harming the user's privacy.

To mitigate this risk, no such low level details are exposed.

The subsections below describe the processing model. At a high level, the information exposed is reduced by the following steps:

  1. Rate-limiting - The user agent notifies the application of changes in the information it can learn. Change notifications are rate-limited.
  2. first-party context - The feature is only available in first-party contexts by default.

11.1.1 Rate-limiting change notifications

We propose exposing the pressure state via rate-limited change notifications. This aims to remove the ability to observe the precise time when a value transitions between two states.

More precisely, once the pressure observer is activated, it will be called once with initial values, and then be called when the values change. The subsequent calls will be rate-limited. When the callback is called, the most recent value is reported.

The specification will recommend a rate limit of at most one call per second for the active window, and one call per 10 seconds for all other windows. We will also recommend that the call timings are jittered across origins.

These measures benefit the user's privacy, by reducing the risk of identifying a device across multiple origins. The rate-limiting also benefits the user's security, by making it difficult to use this API for timing attacks. Last, rate-limiting change callbacks places an upper bound on the performance overhead of this API.

Rate limiting can be implemented in the user agent, but it might also be possible to simply change the polling/sampling rate of the underlying hardware counters, if not accessed via a higher level framework.

11.1.2 No side-channels

It is possible to identify users across non-same origin sites if unique or very precise values can be accessed at the same time by sites not sharing origin.

If the same pressure state and timestamp is observed by two origins, that would be a good indication that the origin is used by the same user on the same machine. For this reason, the API limits reporting pressure state changes to one origin at the time.

A common way to do this, is only to report changes to the focused page, but one of the main users of this API are video conferencing sites. These sites want to make sure that the video streams and effects doesn't negatively affect the system and thus the conferencing experience - but there are two common cases where the site will usually not be focused:

  • The user is taking meeting notes and the site is in the background. Commonly the video stream is only visible via a picture-in-picture window.
  • The user is sharing an external application window such as a presentation, or sharing the whole screen, unusually with some UI indicating sharing is happening.
For this reason, the API considers these two cases to have higher priority than whether the site is focused.

11.1.3 First-party contexts

This API will only be available in frames served from the same origin as the top-level frame. This requirement is necessary for preserving the privacy benefits of the API's quantizing scheme.

The same-origin requirement above implies that the API is only available in first-party contexts by default.

12. Examples

This section is non-normative.

Example 2: How to access observer from callback
const samples = [];

function pressureChange(records, observer) {
  for (const record of records) {
    samples.push(record.state);

    // We only want 20 samples.
    if (samples.length == 20) {
      observer.disconnect();
      return;
    }
  }
}

const observer = new PressureObserver(pressureChange);
observer.observe("cpu");

In the following example we want to lower the number of concurrent video streams when the pressure becomes critical. For the sake of simplicity we only consider this one state.

As lowering the amount of streams might not result in exiting the critical state, or at least not immediately, we use a strategy where we lower one stream at the time every 30 seconds while still in the critical state.

We accomplish this by making sure the callback is called at least once every 30 seconds, or when the state actually changes. When the state changes we reset the interval timer.

Example 3: How to adjust the number of video feeds based on CPU pressure
let timerId = -1;
function pressureChange(records) {
  // Clear timer every time we are called, either by an actual state change,
  // or when called by setTimeout (see below).
  if (timerId > 0) {
    clearTimeout(timerId);
  }

  // When entering critical state, we want to recheck every 30sec if we are
  // still in critical state and if so, further reduce our concurrent streams.
  // For this reason we create a timer for 30 seconds that will call us back
  // with the last result in there were no change.
  const lastRecordArray = [records.at(records.length - 1)];
  timerId = setTimeout(pressureChange.bind(this, lastRecordArray), 30_000);

  for (const record of records) {
    if (record.state == "critical") {
      let streamsCount = getStreamsCount();
      setStreamsCount(streamsCount--);
    }
  }
}

const observer = new PressureObserver(pressureChange);
observer.observe("cpu");

In the following example, we want to demonstrate the usage of takeRecords(), by retrieving the remaining records accumulated since the the callback was last invoked.

It is recommended to do so before disconnect(), otherwise disconnect() will clear them and they will be lost forever.

For example, we might want to measure the pressure during a benchmarking workload, and thus want pressure telemetry for the exact duration of the workload. This means disconnecting all observers immediately when the task is completed, and manually requesting any pending pressure telemetry up to this point that might not have been delivered yet as part of the event loop cycle.

Example 4: How to handle all state changes right up until disconnect
function logWorkloadStatistics(records) {
  // do something with records.
}

const observer = new PressureObserver(logWorkloadStatistics);
observer.observe("cpu");

// Read pending state change records, otherwise they will be cleared
// when we disconnect.
const records = observer.takeRecords();
logWorkloadStatistics(records);

observer.disconnect();

In the following example, we show how to tell the observer to stop watching a specific source by invoking unobserve() with source.

Note
Example 5: How to tell the observer to stop watching for state changes for a specific source
const observer = new PressureObserver(records => { // do something with records. }));

observer.observe("cpu");
observer.observe("gpu");

// Callback now gets called whenever the pressure state changes for 'cpu' or 'gpu'.

observer.unobserve("gpu");

// Callback now only gets called whenever the pressure state changes for 'cpu'.

In the following example, we show how to tell the observer to stop watching for any state changes by calling disconnect(). Calling disconnect() will stop observing all sources observed by previous observe() calls.

Additionally it will clear all pending records collected since the last callback was invoked.

Example 6: how to tell the observer to stop watching for any state changes
const observer = new PressureObserver(records => { // do something with records. });
observer.observe("cpu");
observer.observe("gpu");

// some time later...

observer.disconnect();

// records will be an empty array, because of the previous disconnect().
const records = observer.takeRecords();

13. Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY and RECOMMENDED in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

This specification defines conformance criteria for a single product: a user agent that implements the interfaces that it contains.

A. Acknowledgments

This section is non-normative.

Many thanks for valuable feedback and advice from Anssi Kostiainen, Asaf Yaffe, Chen Xing, Evan Shrubsole, François Beaufort, Jan Gora, Jesse Barnes, Joshua Bell, Kamila Hasanbega, Matt Menke, Moh Haghighat, Nicolás Peña Moreno, Opal Voravootivat, Paul Jensen, Peter Djeu, Raphael Kubo da Costa, Reilly Grant, Ulan Degenbaev, Victor Miura, Wei Wang, and Zhenyao Mo

Special thanks to Amanda Zhao, Fidel Tian, Zhiliang Wang and others from the Zoom engineering team for the feedback and hands-on experiments that have helped improve this API in real-world scenarios.

B. IDL Index

WebIDLenum PressureSource { "thermals", "cpu" };

enum PressureState { "nominal", "fair", "serious", "critical" };

enum PressureFactor { "thermal", "power-supply" };

callback PressureUpdateCallback = undefined (
  sequence<PressureRecord> changes,
  PressureObserver observer
);

[Exposed=(DedicatedWorker,SharedWorker,Window), SecureContext]
interface PressureObserver {
  constructor(PressureUpdateCallback callback, optional PressureObserverOptions options = {});

  Promise<undefined> observe(PressureSource source);
  undefined unobserve(PressureSource source);
  undefined disconnect();
  sequence<PressureRecord> takeRecords();

  [SameObject] static readonly attribute FrozenArray<PressureSource> supportedSources;
};

[Exposed=(DedicatedWorker,SharedWorker,Window), SecureContext]
interface PressureRecord {
  readonly attribute PressureSource source;
  readonly attribute PressureState state;
  readonly attribute FrozenArray<PressureFactor> factors;
  readonly attribute DOMHighResTimeStamp time;
  [Default] object toJSON();
};

dictionary PressureObserverOptions {
  double sampleRate = 1.0;
};

C. References

C.1 Normative references

[dom]
DOM Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://dom.spec.whatwg.org/
[hr-time]
High Resolution Time. Yoav Weiss. W3C. 22 March 2023. W3C Working Draft. URL: https://www.w3.org/TR/hr-time-3/
[html]
HTML Standard. Anne van Kesteren; Domenic Denicola; Ian Hickson; Philip Jägenstedt; Simon Pieters. WHATWG. Living Standard. URL: https://html.spec.whatwg.org/multipage/
[infra]
Infra Standard. Anne van Kesteren; Domenic Denicola. WHATWG. Living Standard. URL: https://infra.spec.whatwg.org/
[mediacapture-streams]
Media Capture and Streams. Cullen Jennings; Bernard Aboba; Jan-Ivar Bruaroey; Henrik Boström; youenn fablet. W3C. 23 March 2023. W3C Candidate Recommendation. URL: https://www.w3.org/TR/mediacapture-streams/
[PERMISSIONS-POLICY]
Permissions Policy. Ian Clelland. W3C. 22 March 2023. W3C Working Draft. URL: https://www.w3.org/TR/permissions-policy-1/
[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119
[RFC8174]
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174
[security-privacy-questionnaire]
Self-Review Questionnaire: Security and Privacy. Theresa O'Connor; Peter Snyder. W3C. 16 December 2021. W3C Working Group Note. URL: https://www.w3.org/TR/security-privacy-questionnaire/
[WEBIDL]
Web IDL Standard. Edgar Chen; Timothy Gu. WHATWG. Living Standard. URL: https://webidl.spec.whatwg.org/

C.2 Informative references

[ECMAScript]
ECMAScript Language Specification. Ecma International. URL: https://tc39.es/ecma262/multipage/