Modernizr tests which native CSS3 and HTML5 features are available in the current UA and makes the results available to you in two ways: as properties on a global
Modernizr object, and as classes on the
<html> element. This information allows you to progressively enhance your pages with a granular level of control over the experience.
This project adheres to the Open Code of Conduct. By participating, you are expected to honor this code.
Often times people want to know when an asynchronous test is done so they can allow their application to react to it.
In the past, you've had to rely on watching properties or
<html> classes. Only events on asynchronous tests are
supported. Synchronous tests should be handled synchronously to improve speed and to maintain consistency.
The new API looks like this:
// Listen to a test, give it a callbackModernizr;
We guarantee that we'll only invoke your function once (per time that you call
on). We are currently not exposing
a method for exposing the
trigger functionality. Instead, if you'd like to have control over async tests, use the
src/addTest feature, and any test that you set will automatically expose and trigger the
Run the test suite
npm install./bin/modernizr -c lib/config-all.json//outputs to ./modernizr.js
grunt buildserve .visit <url>/test
serve the root dir,
Modernizr can be used programmatically via npm:
var modernizr = ;
build method is exposed for generating custom Modernizr builds. Example:
var modernizr = ;modernizr;
The first parameter takes a JSON object of options and feature-detects to include. See
lib/config-all.json for all available options.
The second parameter is a function invoked on task completion.