Quick Tip: Detect CSS3 Support in Browsers with JavaScript

This post is part of a series called CSS3 Mastery.
Subtle CSS3 Typography that you’d Swear was Made in Photoshop
CSS Fundamentals: CSS3 Transitions

Isn't it fun that we get to play with the latest CSS techniques, like shadows and transitions? There's only one problem: how do we compensate, or more importantly, detect the browsers that do not support them? Well, there's a few solutions. In this tutorial and screencast, though, we'll create a JavaScript function that will accept a CSS property name as its parameter, and will return a boolean, indicating whether or not the browser supports the passed property.

Prefer a Video Tutorial?

Press the HD button for a clearer picture.

Step 1

Let's begin by determining how we want to call our function. We'll keep things simple here; something like the following should do the trick:

That should be the final function call. When we pass a CSS property name to the supports() function, it'll return a boolean. If true, we'll attach a className to the documentElement, or <html>. This will then provide us with a new class name to hook onto, from our stylesheet.

Step 2

Next, we'll construct the supports() function.

Why aren't we making supports equal to a standard function? The answer is because we have a bit of prep work to do first, and there's absolutely no reason to repeat those tasks over and over every single time the function is called. In cases like this, it's best to make supports equal to whatever is returned from the self-executing function.

Step 3

To test whether or not the browser supports specific properties, we need to create a *dummy* element, for testing. This generated element will never actually be inserted into the DOM; think of it as a test dummy!

As you're probably aware of, there are a handful of vendor-prefixes that we can use, when working with CSS3 properties:

• -moz
• -webkit
• -o
• -ms
• -khtml

Our JavaScript will need to filter through those prefixes, and test them. So, let's place them in an array; we'll call it, vendors.

Using the split() function to create an array from a string is admittedly lazy, but it saves a handful of seconds!

As we'll be filtering through this array, let's be good boys and girls, and cache the length of the array as well.

The prep work, above, is static, in nature, and doesn't need to be repeated every time we call supports(). This is why we only run it once, when the page loads. Now, let's return the function that will actually be assigned to the supports variable.

The beauty of closures is that, even though supports() is equal to that returned function, it still has access to the div, vendors, and len variables.

Step 4

The immediate test: if the passed property is available to the div's style attribute, we know the browser supports the property; so return true.

Think of, say, the text-shadow CSS3 property. Most modern browsers support it, without the need for a vendor prefix. With that in mind, why filter through all of the prefixes if we don't need to? That's why we place this check at the top.

Step 5

You're likely used to typing CSS3 property names, like so: -moz-box-shadow. However, if, in Firebug, you review the style object, you'll find that it's spelled, MozBoxShadow. As such, if we test:

False will be returned. This value is case-sensitive.

This means that, if the user passes boxShadow to the supports() function, it'll fail. Let's think ahead, and check if the first letter of the argument is lowercase. If it is, we'll fix the error for them.

Regular expressions to the rescue! Above, we're checking if there is a single lowercase letter at the beginning of the string (^). Only on the condition that one is found, we use the toUpperCase() function to capitalize the letter.

Step 6

We next need to filter through the vendors array, and test if there's a match. For instance, if box-shadow is passed, we should test if the style attribute of the div contains any of the following:

If a match is found, we can return true, because the browser does, indeed, provide support for box shadows!

Though we could use a for statement to filter through the array, there's no real need to in this case.

• The order isn't important
• while statements are quicker to type, and require fewer characters
• There's a tiny performance improvement

Don't be confused by vendors[len] + prop; simply replace those names with their real-life values: MozBoxShadow.

Step 7

But, what if none of those values match? In that case, the browser doesn't seem to support the property, in which case we should return false.

That should do it for our function! Let's test it out, by applying a className to the html element, if the browser supports, say, the text-stroke property (which only webkit does).

Step 8: Usage

With a class name that we can now hook onto, let's try it out in our stylesheet.

Final Source Code

For a more comprehensive solution, refer to the Modernizr library.