This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2013-12-12
|
This specification defines an interface for web applications to access timing information related to navigation and elements. It is used by other specifications, like User Timing.
|
|
2013-12-12
|
This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
|
|
2013-10-29
|
This specification defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web applications.
|
|
2012-12-17
|
This document provides an interface for web applications to access timing information related to navigation and elements.
|
|
2012-12-17
|
This specification defines an interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.
|
Group Notes
|
2016-07-20
|
Frame Timing helps web developers measure the performance of their
applications by giving them access to frame performance data to
facilitate smoothness measurements.
|
|
2016-07-20
|
Navigation Error Logging defines an API to store and retrieve error
data related to the previous navigations of a document.
|
Drafts
Below are draft documents:
Proposed Recommendations, Candidate Recommendations, other Working Drafts .
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Proposed Recommendations
|
2017-10-17
|
Page Visibility defines a means to programmatically determine the visibility state of a document. This can aid in the development of power and CPU efficient web applications.
|
|
2017-10-10
|
The requestIdleCallback method is a more appropriate way for scheduling background tasks during times when the browser would otherwise be idle.
|
Candidate Recommendations
|
2018-03-01
|
This specification defines a JavaScript interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.
|
|
2017-10-26
|
This specification defines the preload relationship of the HTML Link Element (<link>).
|
|
2017-04-13
|
This specification defines an interoperable means for site developers to asynchronously transfer data from the user agent to a web server, with the user agent taking the responsibility to eventually send the data.
|
|
2017-03-30
|
This specification defines an interface for web applications to access timing information related to HTML elements.
|
|
2016-12-08
|
This specification extends the High Resolution Time specification by providing methods to store and retrieve high resolution performance metric data.
|
Other Working Drafts
|
2018-02-22
|
This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
|
|
2018-02-15
|
This document describes version 1.0 of the core WebAssembly standard, a safe, portable, low-level code format designed for efficient execution and compact representation.
|
|
2018-02-15
|
This document provides an explicit JavaScript API for interacting with WebAssembly.
|
|
2018-02-15
|
This document describes the integration of WebAssembly with the broader web platform.
|
|
2018-01-15
|
Resource Hints provides hints that authors may use to assist the user
agent in fetching resources to improve page performance.
|
|
2017-12-29
|
Server Timing, part of the performance timeline metrics, provides API
access to request-response cycle performance metrics communicated from
the server to the user agent.
|
|
2017-12-05
|
This document provides an interface for web applications to access timing information related to navigation and elements.
|
|
2017-09-07
|
This document defines an API that web page authors can use to detect presence of “long tasks” that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input.
|
|
2017-09-07
|
This document defines an API that can be used to capture a series of key moments (First Paint, First Contentful Paint) during pageload which developers care about.
|
|
2017-03-29
|
This specification defines an interface for web applications to access the complete timing information for resources in a document.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2017-08-03
|
This specification defines an API that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.
|
|
2016-06-07
|
The reporting API provides a generic reporting framework which allows Web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.
|
|
2015-09-22
|
This document defines an API web page authors can use to write script-based animations where the user agent is in control of limiting the update rate of the animation.
|
|
2014-10-23
|
This specification defines a means for site developers to programmatically give the User Agent hints on the download priority of a resource. This will allow User Agents to more efficiently manage the order in which resources are downloaded.
|