Specification tables

Every reference page on MDN should provide information about the specification or specifications in which that API or technology was defined. This article demonstrates what these tables look like and explains how to add them.

The specifications section definition is similar to the compatibility table definition, is commonly generated from the same data source, and typically appears immediately before it in a page.

Standard specification tables

The standard specification section should look like this:

## Specifications


The {{Specifications}} macro generates the specification table based on the value(s) in the page front-matter.

By default the value(s) in the browser-compat key are used. Each value references a particular feature and its associated compatibility and specification information in the browser-compat-data repository. For example, the text-align page has the following key, which it uses to fetch the associated specification information.

browser-compat: css.property.text-align

Some features are not maintained in the above repository. In these cases, specification information can be added to the page front matter using the spec-urls key. For example, the aria-atomic attribute has the front matter key:

spec-urls: https://w3c.github.io/aria/#aria-atomic

The specifications table for the css.property.text-align key above is rendered in a table as shown:


CSS Logical Properties and Values Level 1
# text-align
CSS Text Module Level 3
# text-align-property

Non-standard features

When documenting a non-standard feature, in particular one that has been removed from a standardization track, don't call the {{Specifications}} macro.

Instead, try to provide information about the feature status and possible alternatives. Examples:

  • This method is no longer on a standardization track. It is kept for compatibility purposes. Use the this other method instead.
  • This method was originally a part of DOM Level 2 Traversal and Range, but is absent in the current DOM specification. This feature is no longer on track to become a standard.
  • This event handler was part of the old WebVR API that has been superseded by the WebXR Device API. It is no longer on track to becoming a standard.