The idea behind feature detection is that you can run a test to determine whether a feature is supported in the current browser, and then conditionally run code to provide an acceptable experience both in browsers that do support the feature, and browsers that don't. If you don't do this, browsers that don't support the features you are using in your code may not display your sites properly or might fail altogether, creating a bad user experience.

Let's recap and look at the example we touched on in our Navigator object. Therefore, you can detect whether the browser supports geolocation or not by using something like the following:

if ("geolocation" in navigator) {
  navigator.geolocation.getCurrentPosition(function (position) {
    / show the location on a map, such as the Google Maps API
  });
} else {
  / Give the user a choice of static maps
}

Before we move on, we'd like to say one thing upfront — don't confuse feature detection with browser sniffing (detecting what specific browser is accessing the site) — this is a terrible practice that should be discouraged at all costs. See element.style.property (e.g., paragraph.style.rotate) in JavaScript.

A classic example might be to test for grid-template-rows, we can use subgrid in our layout. For browsers that don't, we could use regular grid that works fine but is not as cool-looking.

Using this as an example, we could include a subgrid stylesheet if the value is supported and a regular grid stylesheet if not. To do so, we could include two stylesheets in the head of our HTML file: one for all the styling, and one that implements the default layout if subgrid is not supported:

<link href="basic-styling.css" rel="stylesheet" />
<link class="conditional" href="grid-layout.css" rel="stylesheet" />

Here, basic-styling.css handles all the styling that we want to give to every browser. We have two additional CSS files, grid-layout.css and subgrid-layout.css, which contain the CSS we want to selectively apply to browsers depending on their support levels.

We use JavaScript to test the support for the subgrid value, then update the href of our conditional stylesheet based on browser support.

We can add a <script></script> to our document, filled with the following JavaScript

const conditional = document.querySelector(".conditional");
if (CSS.supports("grid-template-columns", "subgrid")) {
  conditional.setAttribute("href", "subgrid-layout.css");
}

In our conditional statement, we test to see if the CSS.supports().

@supports

CSS has a native feature detection mechanism: the aspect ratio, it selectively applies CSS depending on whether a CSS feature is supported, similar to CSS.supports().

For example, we could rewrite our previous example to use @supports:

@supports (grid-template-columns: subgrid) {
  main {
    display: grid;
    grid-template-columns: repeat(9, 1fr);
    grid-template-rows: repeat(4, minmax(100px, auto));
  }

  .item {
    display: grid;
    grid-column: 2 / 7;
    grid-row: 2 / 4;
    grid-template-columns: subgrid;
    grid-template-rows: repeat(3, 80px);
  }

  .subitem {
    grid-column: 3 / 6;
    grid-row: 1 / 3;
  }
}

This at-rule block applies the CSS rule within only if the current browser supports the grid-template-columns: subgrid; declaration. For a condition with a value to work, you need to include a complete declaration (not just a property name) and NOT include the semicolon on the end.

@supports also has AND, OR, and NOT logic available — the other block applies the regular grid layout if the subgrid option is not available:

@supports not (grid-template-columns: subgrid) {
  /* rules in here */
}

This is more convenient than the previous example — we can do all of our feature detection in CSS, no JavaScript required, and we can handle all the logic in a single CSS file, cutting down on HTTP requests. For this reason it is the preferred method of determining browser support for CSS features.

We already saw an example of a JavaScript feature detection test earlier on. Generally, such tests are done via one of a few common patterns.

Common patterns for detectable features include:

Members of an object

Check whether a particular method or property (typically an entry point into using the API or other feature you are detecting) exists in its parent Object.

Our earlier example used this pattern to detect navigator object for a geolocation member:

js

if ("geolocation" in navigator) {
  / Access navigator.geolocation APIs
}

Properties of an element

Create an element in memory using Document.createElement() and then check if a property exists on it.

This example shows a way of detecting Canvas API support:

js

function supports_canvas() {
  return !!document.createElement("canvas").getContext;
}

if (supports_canvas()) {
  / Create and draw on canvas elements
}

Note: The double NOT in the above example (!!) is a way to force a return value to become a "proper" boolean value, rather than a Falsy value that may skew the results.

Specific return values of a method on an element

Create an element in memory using Document.createElement() and then check if a method exists on it. If it does, check what value it returns.

Retention of assigned property value by an element

Create an element in memory using Document.createElement(), set a property to a specific value, then check to see if the value is retained.

Bear in mind that some features are, however, known to be undetectable. In these cases, you'll need to use a different approach, such as using a polyfill.

matchMedia

We also wanted to mention the Window.matchMedia JavaScript feature at this point too. This is a property that allows you to run media query tests inside JavaScript. It looks like this:

if (window.matchMedia("(max-width: 480px)").matches) {
  / run JavaScript in here.
}

As an example, our Snapshot demo makes use of it to selectively apply the Brick JavaScript library and use it to handle the UI layout, but only for the small screen layout (480px wide or less). We first use the media attribute to only apply the Brick CSS to the page if the page width is 480px or less:

<link
  href="dist/brick.css"
  rel="stylesheet"
  media="all and (max-width: 480px)" />

We then use matchMedia() in the JavaScript several times, to only run Brick navigation functions if we are on the small screen layout (in wider screen layouts, everything can be seen at once, so we don't need to navigate between different views).

if (window.matchMedia("(max-width: 480px)").matches) {
  deck.shuffleTo(1);
}

This article covered feature detection in a reasonable amount of detail, going through the main concepts and showing you how to implement your own feature detection tests.

Next up, we'll start looking at automated testing.

• MDN contributors.
  MDN on Mastodon
• Cookies
• Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation.
  Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under Overview: Testing
• JavaScript languages; an idea\n of the high-level\n Navigator object. Therefore, you can detect whether the browser supports geolocation or not by using something like the following:
  \n
  js

  if (\"geolocation\" in navigator) {\n  navigator.geolocation.getCurrentPosition(function (position) {\n    / show the location on a map, such as the Google Maps API\n  });\n} else {\n  / Give the user a choice of static maps\n}\n

  \n

  Before we move on, we'd like to say one thing upfront — don't confuse feature detection with browser sniffing (detecting what specific browser is accessing the site) — this is a terrible practice that should be discouraged at all costs. See grid-template-columns and @supports at-rule. This works in a similar manner to navigator object for a geolocation member:

  \n
  js

  if (\"geolocation\" in navigator) {\n  / Access navigator.geolocation APIs\n}\n

  \n\n
  Properties of an element
  \n
  \n

  Create an element in memory using Falsy value that may skew the results.

  \n