Web Media API Snapshot 2024

Final Community Group Report

This version:
https://www.w3.org/community/reports/webmediaapi/CG-FINAL-webmediaapi-20241016/
Latest editor's draft:
https://w3c.github.io/webmediaapi/
Previous version:
https://www.w3.org/2023/11/webmediaapi.html
Test suite:
https://webapitests2024.ctawave.org/
Editors:
Jon Piesing (TP Vision Belgium N.V.)
John Riviello (Comcast)
Former editors:
David Evans (British Broadcasting Corporation)
John Luther (JW Player)
Mark Vickers (Comcast)
Feedback:
GitHub w3c/webmediaapi (pull requests, new issue, open issues)

Abstract

This specification lists the web APIs to support media web apps that are supported across all four of the most widely used user agent code bases at the time of publication (i.e., Chrome, Edge, Firefox, and Safari). This specification should be updated at least annually to keep pace with the evolving web platform. We encourage manufacturers to develop products that support the APIs in the most recent version of Web Media API Snapshot. This specification is comprised of references to existing specifications in W3C and other specification groups. The target devices will include any device that runs a modern HTML user agent, including televisions, game machines, set-top boxes, mobile devices and personal computers.

Status of This Document

This specification was published jointly by the Web Media API Community Group and the Consumer Technology Association (CTA) as part of the CTA WAVE Project.

It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups.

GitHub Issues are preferred for discussion of this specification.

1. Introduction

This section is non-normative.

Writing portable media web apps across browsers on consumer products (e.g. smart TVs, game machines, set-top boxes) is much more difficult than writing portable media web apps across personal computer browsers. Two main reasons for this are that the browsers on consumer products are often quite out-of-date and that they often have integration issues.

1.1 Out-of-date browsers

While browsers integrated into consumer products are often built from the same major HTML user agent code bases as personal computer browsers, it is not unusual for a consumer product to be using a code base release that is three or more years old, while personal computer browsers use recent code base releases. Furthermore, browsers on consumer products are often infrequently updated, if ever. This results in very different web API support across devices.

This specification is intended to address this problem by listing key specifications used by media web apps that are all supported in common by all of the four major web user agent code bases at the time of publication (i.e., Chrome, Edge, Firefox, and Safari). The specification will then be used to generate a test suite. The versions of each of the four code bases used to generate the test suite are listed on the front page of the test suite. (See Test suite URL above.)

The specification and test suite enable device manufacturers to specify and verify that their browsers are up-to-date with current web standards at the time of product release. The specification and tests can also be used to specify and verify updates to browsers in the field.

Note that this specification is not defining a subset or profile to be used in place of the full web platform. There are additional specifications that are included in all code bases that are not included in this specification. Furthermore, individual code bases include APIs that are not supported on all other code bases, but are nonetheless widely used. Therefore, this specification and associated tests should only be used as verification of a minimum set of current APIs. There is no suggestion that APIs not included in this specification should be removed from implementations.

It is intended that this specification be updated periodically to reflect adoption of new specifications in the web platform. For example, the specification might be updated once a year for media devices being introduced onto the market in the following year.

1.2 Integration issues

There are many issues during integration of a web user agent with a hardware device that can affect the operation of web APIs. For example, if insufficient memory is allocated for cookies, they won’t function as intended.

To address this issue, this specification includes a list of target values for several APIs which are known to have been impacted by integration issues. There will also be a test suite to verify these values are supported on a device. It is expected that additional integration requirements will be added in future updates.

Note that these values are not mandated by any web standards, but are based on measurement of values supported by popular browsers. Supporting these values should provide better interoperability of web applications with personal computer and mobile browsers. Manufacturers may choose to exceed these values based on their expected application environments.

2. 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 MUST and SHOULD 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.

3. Web Media APIs currently supported on all platforms

3.1 Introduction

This section is non-normative.

This section lists the web APIs to support media web apps that are supported across all four of the most widely used user agent code bases at the time of publication (i.e., Chrome, Edge, Firefox, and Safari). We encourage manufacturers to develop products that support the APIs in the most recent version of this specification.

The approach taken in this draft is only to include specifications that are of particular significance to authors, but not include all the specifications cited by those included specifications. For example, HTTP is required by the HTML spec and is therefore not included here.

In addition, the specifications of the web APIs mentioned here may in turn (recursively) reference other specifications that are not supported across all four of the most widely used user agent code bases. This possibility is understood and accepted. For example, Content Security Policy Level 2 [CSP2] references the image() function from CSS Images Module Level 4 [CSS-IMAGES-4], but CSS Images Module Level 4 is not yet widely supported. These unsupported referenced specifications are not explicitly cited as exceptions in this specification but, in spite of this, will not be tested as part of our tests.

3.1.1 Features with limited implementation

Parts of some web specifications are not currently implemented across all user agent code bases and may never be. Consequently, these features will not be included in our tests. Any such features are noted as exceptions under that API.

3.1.2 At-risk features

Some specifications referenced in this section may not have reached Recommendation and, as such, may contain 'at-risk' features. Since the most common reason for features being marked as at-risk is lack of implementations, such features may not be present in some implementations of this specification and will not be tested as part of our tests.

3.1.3 Hardware Limitations

While this specification does not specify a minimum or maximum number of media elements that can play content simultaneously, developers should note that due to hardware limitations of available decoders, the simultaneous playback of multiple media elements in a web application may not be possible.

3.2 Client code updates

The W3C Technical Architecture Group released a finding called The evergreen Web which strongly recommends that "Browsers must be regularly updated, especially to fix security and interoperability bugs — ideally with an automatic, secure update mechanism." [EVERGREEN-WEB]

Devices SHOULD regularly update their browsers, preferably automatically.

3.3 Core web specifications

Devices MUST be conforming implementations of the following specifications:

3.4 CSS specifications

Devices MUST be conforming implementations of the following specifications, which are derived from the official Cascading Style Sheets definition from CSS Snapshot 2023 [CSS-2023] as well as more recent revisions to CSS specifications as appropriate:

3.5 Media specifications

Devices MUST be conforming implementations of the following specifications:

3.6 Graphics specifications

Devices MUST be conforming implementations of the following specifications:

3.7 Font specifications

Devices MUST be conforming implementations of the following specifications:

3.8 Networking specifications

Devices MUST be conforming implementations of the following specifications:

3.9 Security specifications

Devices MUST be conforming implementations of the following specifications:

Note: Along with these security standards for the user agent, all IoT devices should be designed with security in mind. An industry-developed voluntary consensus standard for a minimum security "baseline" for IoT devices can be found at https://shop.cta.tech/collections/standards/cybersecurity.

3.10 Web Performance specifications

Devices MUST be conforming implementations of the following specifications:

3.11 Other web specifications

Devices MUST be conforming implementations of the following specifications:

4. User Agent Integration Specifications

4.1 Introduction

This section is non-normative.

This section contains values for integrating a web user agent with a consumer device. The values are based on de facto requirements from browsers on personal computers and mobile devices. Supporting these integration specifications will increase interoperability with media web apps on other devices.

A test suite will evaluate client support for these specifications.

4.2 Cookies

4.3 URLs

5. Web Media APIs proposed to be supported on all platforms

This section is non-normative.

5.1 Introduction

APIs in this section are important for web media delivery, but either are not yet implemented in all four code bases or not yet commonly implemented across embedded browsers in consumer products, such as WPEWebKit. We encourage the following APIs be implemented on all HTML user agents as soon as possible. It is expected that, as implementations become available, some of these specifications may be listed as supported on all platforms in a future version of this specification.

5.2 Media specifications

5.3 WebAssembly specifications

5.4 Other web specifications

A. Annex A: WMAS Bindings (normative)

This annex lists Web Media API bindings assigned within the CTA namespace "urn:cta". These bindings may be used to signal compatibility intent or requirement for the WAVE API Snapshot identified in the binding.

See https://www.iana.org/assignments/urn-formal/cta for the CTA namespace registration in the Official IANA Registry of URN Namespaces [IANA-URN-NAMESPACES].

The table below is normative within this specification. For more information on these bindings contact standards@CTA.tech.

CTA Identifier Referenced Specification
urn:cta:wave:appinformation:standardversion:cta5000:2017 Web Media API Snapshot 2017 CTA-5000 [CTA-5000]
urn:cta:wave:appinformation:standardversion:cta5000a:2018 Web Media API Snapshot 2018 CTA-5000-A [CTA-5000-A]
urn:cta:wave:appinformation:standardversion:cta5000b:2019 Web Media API Snapshot 2019 CTA-5000-B [CTA-5000-B]
urn:cta:wave:appinformation:standardversion:cta5000c:2020 Web Media API Snapshot 2020 CTA-5000-C [CTA-5000-C]
urn:cta:wave:appinformation:standardversion:cta5000d:2021 Web Media API Snapshot 2021 CTA-5000-D [CTA-5000-D]
urn:cta:wave:appinformation:standardversion:cta5000e:2022 Web Media API Snapshot 2022 CTA-5000-E [CTA-5000-E]
urn:cta:wave:appinformation:standardversion:cta5000f:2023 Web Media API Snapshot 2023 CTA-5000-F [CTA-5000-F]
urn:cta:wave:appinformation:standardversion:cta5000g:2024 Web Media API Snapshot 2024 CTA-5000-G [CTA-5000-G]

B. References

For WHATWG living standards, while it is recommended that devices support the living standard, they must support the referenced review draft version of each WHATWG standard or a later commit snapshot version.

B.1 Normative references

[2DCONTEXT]
HTML Canvas 2D Context. Rik Cabanier; Jatinder Mann; Jay Munro; Tom Wiltzius; Ian Hickson. W3C. 28 January 2021. W3C Recommendation. URL: https://www.w3.org/TR/2dcontext/
[BEACON]
Beacon. Ilya Grigorik; Alois Reitbauer. W3C. 3 August 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/beacon/
[COMPOSITING]
Compositing and Blending Level 1. Chris Harrelson. W3C. 21 March 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/compositing-1/
[CSP2]
Content Security Policy Level 2. Mike West; Adam Barth; Daniel Veditz. W3C. 15 December 2016. W3C Recommendation. URL: https://www.w3.org/TR/CSP2/
[CSS-ANIMATIONS-1]
CSS Animations Level 1. David Baron; Dean Jackson; Tab Atkins Jr.; Brian Birtles. W3C. 2 March 2023. W3C Working Draft. URL: https://www.w3.org/TR/css-animations-1/
[CSS-BOX-3]
CSS Box Model Module Level 3. Elika Etemad. W3C. 11 April 2024. W3C Recommendation. URL: https://www.w3.org/TR/css-box-3/
[CSS-CASCADE-4]
CSS Cascading and Inheritance Level 4. Elika Etemad; Tab Atkins Jr.. W3C. 13 January 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-cascade-4/
[CSS-COLOR-4]
CSS Color Module Level 4. Chris Lilley; Tab Atkins Jr.; Lea Verou. W3C. 13 February 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-color-4/
[CSS-CONTAIN-1]
CSS Containment Module Level 1. Tab Atkins Jr.; Florian Rivoal. W3C. 25 June 2024. W3C Recommendation. URL: https://www.w3.org/TR/css-contain-1/
[CSS-COUNTER-STYLES-3]
CSS Counter Styles Level 3. Tab Atkins Jr.. W3C. 27 July 2021. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-counter-styles-3/
[CSS-EASING-1]
CSS Easing Functions Level 1. Brian Birtles; Dean Jackson; Matt Rakow. W3C. 13 February 2023. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-easing-1/
[CSS-FLEXBOX-1]
CSS Flexible Box Layout Module Level 1. Tab Atkins Jr.; Elika Etemad; Rossen Atanassov; David Baron. W3C. 19 November 2018. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-flexbox-1/
[CSS-FONT-LOADING-3]
CSS Font Loading Module Level 3. Tab Atkins Jr.. W3C. 6 April 2023. W3C Working Draft. URL: https://www.w3.org/TR/css-font-loading-3/
[CSS-FONTS-3]
CSS Fonts Module Level 3. John Daggett; Myles Maxfield; Chris Lilley. W3C. 20 September 2018. W3C Recommendation. URL: https://www.w3.org/TR/css-fonts-3/
[CSS-GRID-1]
CSS Grid Layout Module Level 1. Tab Atkins Jr.; Elika Etemad; Rossen Atanassov; Oriol Brufau. W3C. 18 December 2020. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-grid-1/
[CSS-IMAGES-3]
CSS Images Module Level 3. Tab Atkins Jr.; Elika Etemad; Lea Verou. W3C. 18 December 2023. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-images-3/
[CSS-LOGICAL-1]
CSS Logical Properties and Values Level 1. Rossen Atanassov; Elika Etemad. W3C. 27 August 2018. W3C Working Draft. URL: https://www.w3.org/TR/css-logical-1/
[CSS-MULTICOL-1]
CSS Multi-column Layout Module Level 1. Florian Rivoal; Rachel Andrew. W3C. 16 May 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-multicol-1/
[CSS-NAMESPACES-3]
CSS Namespaces Module Level 3. Elika Etemad. W3C. 20 March 2014. W3C Recommendation. URL: https://www.w3.org/TR/css-namespaces-3/
[CSS-SCROLL-SNAP-1]
CSS Scroll Snap Module Level 1. Matt Rakow; Jacob Rossi; Tab Atkins Jr.; Elika Etemad. W3C. 11 March 2021. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-scroll-snap-1/
[CSS-SHAPES-1]
CSS Shapes Module Level 1. Rossen Atanassov; Alan Stearns. W3C. 15 November 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-shapes-1/
[CSS-STYLE-ATTR]
CSS Style Attributes. Tantek Çelik; Elika Etemad. W3C. 7 November 2013. W3C Recommendation. URL: https://www.w3.org/TR/css-style-attr/
[CSS-SYNTAX-3]
CSS Syntax Module Level 3. Tab Atkins Jr.; Simon Sapin. W3C. 24 December 2021. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-syntax-3/
[CSS-TEXT-DECOR-3]
CSS Text Decoration Module Level 3. Elika Etemad; Koji Ishii. W3C. 5 May 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-text-decor-3/
[CSS-TRANSFORMS-1]
CSS Transforms Module Level 1. Simon Fraser; Dean Jackson; Theresa O'Connor; Dirk Schulze. W3C. 14 February 2019. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-transforms-1/
[CSS-TRANSITIONS-1]
CSS Transitions. David Baron; Dean Jackson; Brian Birtles; David Hyatt. W3C. 11 October 2018. W3C Working Draft. URL: https://www.w3.org/TR/css-transitions-1/
[CSS-UI-3]
CSS Basic User Interface Module Level 3 (CSS3 UI). Tantek Çelik; Florian Rivoal. W3C. 21 June 2018. W3C Recommendation. URL: https://www.w3.org/TR/css-ui-3/
[CSS-VALUES]
CSS Values and Units Module Level 3. Tab Atkins Jr.; Elika Etemad. W3C. 22 March 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-values-3/
[CSS-VARIABLES-1]
CSS Custom Properties for Cascading Variables Module Level 1. Tab Atkins Jr.. W3C. 16 June 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-variables-1/
[CSS-WILL-CHANGE-1]
CSS Will Change Module Level 1. Tab Atkins Jr.. W3C. 5 May 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-will-change-1/
[CSS-WRITING-MODES-3]
CSS Writing Modes Level 3. Elika Etemad; Koji Ishii. W3C. 10 December 2019. W3C Recommendation. URL: https://www.w3.org/TR/css-writing-modes-3/
[CSS2]
Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification. Bert Bos; Tantek Çelik; Ian Hickson; Håkon Wium Lie. W3C. 7 June 2011. W3C Recommendation. URL: https://www.w3.org/TR/CSS21/
[CSS3-BACKGROUND]
CSS Backgrounds and Borders Module Level 3. Elika Etemad; Brad Kemper. W3C. 11 March 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-backgrounds-3/
[CSS3-CONDITIONAL]
CSS Conditional Rules Module Level 3. Chris Lilley; David Baron; Elika Etemad. W3C. 15 August 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-conditional-3/
[CSSOM-VIEW]
CSSOM View Module. Simon Pieters. W3C. 17 March 2016. W3C Working Draft. URL: https://www.w3.org/TR/cssom-view-1/
[CTA-5000]
Web Media API Snapshot 2017 CTA-5000. David Evans; Mark Vickers. Consumer Technology Association. December 2017. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-final-v2_pdf.pdf
[CTA-5000-A]
Web Media API Snapshot 2018 CTA-5000-A. Jon Piesing; Mark Vickers. Consumer Technology Association. December 2018. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-a-final.pdf
[CTA-5000-B]
Web Media API Snapshot 2019 CTA-5000-B. John Luther; Jon Piesing; John Riviello. Consumer Technology Association. December 2019. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-b-final_v2.pdf
[CTA-5000-C]
Web Media API Snapshot 2020 CTA-5000-C. Jon Piesing; John Riviello. Consumer Technology Association. December 2020. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-c_final.pdf
[CTA-5000-D]
Web Media API Snapshot 2021 CTA-5000-D. Jon Piesing; John Riviello. Consumer Technology Association. December 2021. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-d-final.pdf
[CTA-5000-E]
Web Media API Snapshot 2022 CTA-5000-E. Jon Piesing; John Riviello. Consumer Technology Association. December 2022. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-e-final.pdf
[CTA-5000-F]
Web Media API Snapshot 2023 CTA-5000-F. Jon Piesing; John Riviello. Consumer Technology Association. October 2023. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-f-final.pdf
[CTA-5000-G]
Web Media API Snapshot 2024 CTA-5000-G. Jon Piesing; John Riviello. Consumer Technology Association. October 2024. CTA Specification. URL: https://cdn.cta.tech/cta/media/media/resources/standards/pdfs/cta-5000-g-final.pdf
[DOM]
DOM Standard. Anne van Kesteren. WHATWG. 19 June 2023. Review Draft (use this version or later). URL: https://dom.spec.whatwg.org/review-drafts/2023-06/
[ECMASCRIPT-2024]
ECMA-262 15th Edition, The ECMAScript 2024 Language Specification. Shu-yu Guo; Michael Ficarra; Kevin Gibbons. Ecma International. June 2024. Standard. URL: https://262.ecma-international.org/15.0/
[ENCRYPTED-MEDIA-1]
Encrypted Media Extensions. David Dorwin; Jerry Smith; Mark Watson; Adrian Bateman. W3C. 18 September 2017. W3C Recommendation. URL: https://www.w3.org/TR/encrypted-media-1/
[FETCH]
Fetch Standard. Anne van Kesteren. WHATWG. 18 December 2023. Review Draft (use this version or later). URL: https://fetch.spec.whatwg.org/review-drafts/2023-12/
[FILEAPI]
File API. Marijn Kruisselbrink. W3C. 24 May 2024. W3C Working Draft. URL: https://www.w3.org/TR/FileAPI/
[FILTER-EFFECTS-1]
Filter Effects Module Level 1. Dirk Schulze; Dean Jackson. W3C. 18 December 2018. W3C Working Draft. URL: https://www.w3.org/TR/filter-effects-1/
[FULLSCREEN]
Fullscreen API Standard. Philip Jägenstedt. WHATWG. 17 July 2023. Review Draft (use this version or later). URL: https://fullscreen.spec.whatwg.org/review-drafts/2023-07/
[GETUSERMEDIA]
Media Capture and Streams. Cullen Jennings; Bernard Aboba; Jan-Ivar Bruaroey; Henrik Boström; youenn fablet. W3C. 3 October 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/mediacapture-streams/
[GIF]
Graphics Interchange Format. CompuServe Incorporated. 31 July 1990. URL: https://www.w3.org/Graphics/GIF/spec-gif89a.txt
[HR-TIME-3]
High Resolution Time. Yoav Weiss. W3C. 19 July 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. 15 January 2024. Review Draft (use this version or later). URL: https://html.spec.whatwg.org/review-drafts/2024-01/
[IANA-URN-NAMESPACES]
Uniform Resource Names (URN) Namespaces. IANA. URL: https://www.iana.org/assignments/urn-namespaces/
[INDEXEDDB]
Indexed Database API. Nikunj Mehta; Jonas Sicking; Eliot Graff; Andrei Popescu; Jeremy Orlow; Joshua Bell. W3C. 8 January 2015. W3C Recommendation. URL: https://www.w3.org/TR/IndexedDB/
[JPEG]
JPEG File Interchange Format. Eric Hamilton. C-Cube Microsystems. Milpitas, CA, USA. September 1992. URL: https://www.w3.org/Graphics/JPEG/jfif3.pdf
[MEDIA-CAPABILITIES]
Media Capabilities. Jean-Yves Avenard; Mark Foltz. W3C. 7 October 2024. W3C Working Draft. URL: https://www.w3.org/TR/media-capabilities/
[MEDIA-FRAGS]
Media Fragments URI 1.0 (basic). Raphaël Troncy; Erik Mannens; Silvia Pfeiffer; Davy Van Deursen. W3C. 25 September 2012. W3C Recommendation. URL: https://www.w3.org/TR/media-frags/
[MEDIA-SOURCE-1]
Media Source Extensions™. Matthew Wolenetz; Jerry Smith; Mark Watson; Aaron Colwell; Adrian Bateman. W3C. 17 November 2016. W3C Recommendation. URL: https://www.w3.org/TR/media-source-1/
[MEDIAQUERIES-4]
Media Queries Level 4. Florian Rivoal; Tab Atkins Jr.. W3C. 25 December 2021. W3C Candidate Recommendation. URL: https://www.w3.org/TR/mediaqueries-4/
[NAVIGATION-TIMING]
Navigation Timing. Zhiheng Wang. W3C. 17 December 2012. W3C Recommendation. URL: https://www.w3.org/TR/navigation-timing/
[NOTIFICATIONS]
Notifications API Standard. Anne van Kesteren. WHATWG. 17 July 2023. Review Draft (use this version or later). URL: https://notifications.spec.whatwg.org/review-drafts/2023-07/
[OPEN-FONT-FORMAT]
Information technology — Coding of audio-visual objects — Part 22: Open Font Format. International Organization for Standardization. URL: http://standards.iso.org/ittf/PubliclyAvailableStandards/c052136_ISO_IEC_14496-22_2009%28E%29.zip
[PERFORMANCE-TIMELINE]
Performance Timeline. Nicolas Pena Moreno. W3C. 16 February 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/performance-timeline/
[PNG2e-20031110]
Portable Network Graphics (PNG) Specification (Second Edition). David Duce. W3C. 10 November 2003. W3C Recommendation. URL: https://www.w3.org/TR/2003/REC-PNG-20031110/
[REFERRER-POLICY]
Referrer Policy. Jochen Eisinger; Emily Stark. W3C. 26 January 2017. W3C Candidate Recommendation. URL: https://www.w3.org/TR/referrer-policy/
[RESIZE-OBSERVER-1]
Resize Observer. Aleks Totic; Greg Whitworth. W3C. 11 February 2020. W3C Working Draft. URL: https://www.w3.org/TR/resize-observer-1/
[RESOURCE-TIMING-1]
Resource Timing. Yoav Weiss; Noam Rosenthal. W3C. 24 May 2024. W3C Candidate Recommendation. URL: https://www.w3.org/TR/resource-timing/
[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
[RFC5246]
The Transport Layer Security (TLS) Protocol Version 1.2. T. Dierks; E. Rescorla. IETF. August 2008. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc5246
[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
[RFC8446]
The Transport Layer Security (TLS) Protocol Version 1.3. E. Rescorla. IETF. August 2018. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc8446
[SELECT]
Selectors Level 3. Tantek Çelik; Elika Etemad; Daniel Glazman; Ian Hickson; Peter Linss; John Williams. W3C. 6 November 2018. W3C Recommendation. URL: https://www.w3.org/TR/selectors-3/
[SERVICE-WORKERS-1]
Service Workers. Jake Archibald; Marijn Kruisselbrink. W3C. 12 July 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/service-workers/
[SRI]
Subresource Integrity. Devdatta Akhawe; Frederik Braun; Francois Marier; Joel Weinberger. W3C. 23 June 2016. W3C Recommendation. URL: https://www.w3.org/TR/SRI/
[UIEVENTS]
UI Events. Gary Kacmarcik; Travis Leithead. W3C. 7 September 2024. W3C Working Draft. URL: https://www.w3.org/TR/uievents/
[UPGRADE-INSECURE-REQUESTS]
Upgrade Insecure Requests. Mike West. W3C. 8 October 2015. W3C Candidate Recommendation. URL: https://www.w3.org/TR/upgrade-insecure-requests/
[USER-TIMING-2]
User Timing Level 2. Ilya Grigorik. W3C. 26 February 2019. W3C Recommendation. URL: https://www.w3.org/TR/user-timing-2/
[WEB-ANIMATIONS]
Web Animations. Brian Birtles; Robert Flack; Stephen McGruer; Antoine Quint. W3C. 5 June 2023. W3C Working Draft. URL: https://www.w3.org/TR/web-animations-1/
[WEBAUDIO]
Web Audio API. Paul Adenot; Hongchan Choi. W3C. 17 June 2021. W3C Recommendation. URL: https://www.w3.org/TR/webaudio/
[WEBCRYPTOAPI]
Web Cryptography API. Mark Watson. W3C. 26 January 2017. W3C Recommendation. URL: https://www.w3.org/TR/WebCryptoAPI/
[WEBGL-103]
WebGL Specification. Dean Jackson. Khronos. 27 October 2014. URL: https://www.khronos.org/registry/webgl/specs/1.0.3/
[WEBRTC]
WebRTC: Real-Time Communication in Browsers. Cullen Jennings; Jan-Ivar Bruaroey; Henrik Boström; Florent Castelli. W3C. 8 October 2024. W3C Recommendation. URL: https://www.w3.org/TR/webrtc/
[WEBSOCKETS]
WebSockets Standard. Adam Rice. WHATWG. 18 September 2023. Review Draft (use this version or later). URL: https://websockets.spec.whatwg.org/review-drafts/2023-09/
[WOFF]
WOFF File Format 1.0. Jonathan Kew; Tal Leming; Erik van Blokland. W3C. 13 December 2012. W3C Recommendation. URL: https://www.w3.org/TR/WOFF/
[XHR]
XMLHttpRequest Standard. Anne van Kesteren. WHATWG. 19 February 2024. Review Draft (use this version or later). URL: https://xhr.spec.whatwg.org/review-drafts/2024-02/

B.2 Informative references

[APPMANIFEST]
Web Application Manifest. Marcos Caceres; Kenneth Christiansen; Diego Gonzalez-Zuniga; Daniel Murphy; Christian Liebel. W3C. 11 October 2024. W3C Working Draft. URL: https://www.w3.org/TR/appmanifest/
[CSS-2023]
CSS Snapshot 2023. Chris Lilley; Elika Etemad; Tab Atkins Jr.; Florian Rivoal. W3C. 7 December 2023. W3C Working Group Note. URL: https://www.w3.org/TR/css-2023/
[CSS-IMAGES-4]
CSS Images Module Level 4. Tab Atkins Jr.; Elika Etemad; Lea Verou. W3C. 17 February 2023. W3C Working Draft. URL: https://www.w3.org/TR/css-images-4/
[EVERGREEN-WEB]
The evergreen Web. Hadley Beeman. W3C. 9 February 2017. TAG Finding. URL: https://www.w3.org/2001/tag/doc/evergreen-web/
[INBANDTRACKS]
Sourcing In-band Media Resource Tracks from Media Containers into HTML. Silvia Pfeiffer; Bob Lund. W3C. 26 April 2015. Unofficial Draft. URL: https://dev.w3.org/html5/html-sourcing-inband-tracks/
[MEDIASESSION]
Media Session. Thomas Steimel; youenn fablet. W3C. 4 October 2024. W3C Working Draft. URL: https://www.w3.org/TR/mediasession/
[PUSH-API]
Push API. Peter Beverloo; Martin Thomson; Marcos Caceres. W3C. 3 September 2024. W3C Working Draft. URL: https://www.w3.org/TR/push-api/
[WASM-CORE-1]
WebAssembly Core Specification. Andreas Rossberg. W3C. 5 December 2019. W3C Recommendation. URL: https://www.w3.org/TR/wasm-core-1/
[WASM-JS-API-1]
WebAssembly JavaScript Interface. Daniel Ehrenberg. W3C. 5 December 2019. W3C Recommendation. URL: https://www.w3.org/TR/wasm-js-api-1/
[WASM-WEB-API-1]
WebAssembly Web API. Daniel Ehrenberg. W3C. 5 December 2019. W3C Recommendation. URL: https://www.w3.org/TR/wasm-web-api-1/
[WEBCODECS]
WebCodecs. Paul Adenot; Bernard Aboba; Eugene Zemtsov. W3C. 8 October 2024. W3C Working Draft. URL: https://www.w3.org/TR/webcodecs/
[WEBTRANSPORT]
WebTransport. Bernard Aboba; Nidhi Jaju; Victor Vasiliev. W3C. 31 May 2024. W3C Working Draft. URL: https://www.w3.org/TR/webtransport/