API event subpage template

Note: Remove this whole explanatory note before publishing.

Page front matter:

The front matter at the top of the page is used to define "page metadata". The values should be updated appropriately for the particular event.

title: "NameOfTheParentInterface: NameOfTheEvent event"
slug: Web/API/NameOfTheParentInterface/NameOfTheEvent_event
page-type: web-api-event
  - experimental
  - deprecated
  - non-standard
browser-compat: path.to.feature.NameOfTheEvent_event

Title heading displayed at the top of the page. Format as "NameOfTheParentInterface: NameOfTheEvent event". For example, the animationcancel event of the Window interface has a title of Window: animationcancel event.


The end of the URL path after https://developer.mozilla.org/en-US/docs/. This will be formatted like Web/API/NameOfTheParentInterface/NameOfTheEvent_event.


The page-type key for Web/API events is always web-api-event.


Flags describing the status of this feature. An array which may contain one or more of the following: experimental, deprecated, non-standard. This key should not be set manually: it is set automatically based on values in the browser compatibility data for the feature. See How to add or update feature statuses.


Replace the placeholder value path.to.feature.NameOfTheEvent_event with the query string for the event in the Browser compat data repo. The toolchain automatically uses the key to populate the compatibility and specification sections (replacing the {{Compat}} and {{Specifications}} macros).

Note that you may first need to create/update an entry for the event in our Browser compat data repo, and this entry will need to include specification information. See our guide on how to do this.

Top-of-page macros

A number of macro calls appear at the top of the content section (immediately below the page frontmatter). These macros are automatically added by the toolchain (there is no need to add/remove):

  • {{SeeCompatTable}} — this generates a This is an experimental technology banner that indicates the technology is experimental. If it is experimental, and the technology is hidden behind a pref in Firefox, you should also fill in an entry for it in the Experimental features in Firefox page.
  • {{Deprecated_Header}} — this generates a Deprecated banner that indicates that use of the technology is discouraged.
  • {{Non-standard_Header}} — this generates a Non-standard banner that indicates that the feature is not part of any specification.

You should update or delete the following macros according to the advice below:

  • {{SecureContext_Header}} — this generates a Secure context banner that indicates the technology is only available in a secure context. If it isn't, then you can remove the macro call. If it is, then you should also fill in an entry for it in the Features restricted to secure contexts page.
  • {{APIRef("GroupDataName")}} — this generates the left-hand reference sidebar showing quick reference links related to the current page. For example, every page in the WebVR API has the same sidebar, which points to the other pages in the API. To generate the correct sidebar for your API, you need to add a GroupData entry to our GitHub repo, and include the entry's name inside the macro call in place of GroupDataName. See our API reference sidebars guide for information on how to do this. Remember to remove the {{MDNSidebar}} macro when you copy this page.

Do not provide status header macros manually. Refer to the section "How to add or update feature statuses" to add these statuses to the page.

Samples of the Secure context, Experimental, Deprecated, and Non-standard banners are shown right after this note block.

Parent object link

Add a link to this new page from its parent object's Events section. For example, Element: wheel event is linked from Element Events.

If the parent object does not have an Events section, then add one. If this is a new "class" of event, then you should add a link to this section of the parent from the Event reference.

Remember to remove this whole explanatory note before publishing.

Secure context: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.

Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Non-standard: This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

Begin the content on the page with an introductory paragraph — start by naming the event, saying what interface it is part of, and saying what it does. This should ideally be one or two short sentences. You could copy most of this from the property's summary on the corresponding API reference page.


Use the event name in methods like addEventListener(), or set an event handler property.

addEventListener("NameOfTheEvent", (event) => {});

onNameOfTheEvent = (event) => {};

Event type

If the event has a special type, mention it along with its inheritance. If not, indicate that it is a generic event:

A generic Event.

Or, for example:

An XRSessionEvent. Inherits from Event.

Event XRSessionEvent

Event properties

If the event is not just a generic Event, list the additional properties the event has.

In addition to the properties listed below, properties from the parent interface, Event, are available.

session Read only

The XRSession to which the event refers.


If you want to provide additional text (too long for the summary), add a Description section. It may contain the headings



Use cases

which can provide more information.


Note that we use the plural "Examples" even if the page only contains one example.

A descriptive heading

Each example must have an H3 heading (###) naming the example. The heading should be descriptive of what the example is doing. For example, "A simple example" does not say anything about the example and therefore, not a good heading. The heading should be concise. For a longer description, use the paragraph after the heading.

See our guide on how to add code examples for more information.

Note: Sometimes you will want to link to examples given on another page.

Scenario 1: If you have some examples on this page and some more examples on another page:

Include an H3 heading (###) for each example on this page and then a final H3 heading (###) with the text "More examples", under which you can link to the examples on other pages. For example:

## Examples

### Using the fetch API

Example of Fetch

### More examples

Links to more examples on other pages

Scenario 2: If you only have examples on another page and none on this page:

Don't add any H3 headings; just add the links directly under the H2 heading "Examples". For example:

## Examples

For examples of this API, see [the page on fetch()](https://example.org).



To use this macro, remove the backticks and backslash in the markdown file.

Browser compatibility


To use this macro, remove the backticks and backslash in the markdown file.

See also

Include links to reference pages and guides related to the current API. For more guidelines, see the See also section in the Writing style guide.

  • link1
  • link2
  • external_link (year)