This will give you a JSON file that you will give to the Modernizr module to make your custom build.
Chrome added support for this in v19, but removed it again in v24 because of "a number of areas for development in both the API and specific user experience in Chrome".
No other browsers currently support it, however a Java Script shim is available.
This configuration file can be used with grunt-modernizr to automatically build your custom version.
Just add it to your Gruntfile, and you are off to the races. Since we only look at the returned value from any feature detection function, you do not need to actually use a function.
With this knowledge that Modernizr gives you, you can take advantage of these new features in the browsers that can render or utilize them, and still have easy and reliable means of controlling the situation for the browsers that cannot.
In the dark ages of web development, we often had to resort to ™?
Now you have to go back and audit your code, updating every single place that you are doing this check.
That is assuming that you have the time to find out about every feature update for every single browser. There is, and it is called ™, your code works there - automatically! The code ends up being similar, but much more clear to its actual intention A lot has changed since the last version of Modernizr. Instead, just head over to the Download page as you could have previously, and select the features you want to use in your project.
Modernizr is a small piece of Java Script code that automatically detects the availability of next-generation web technologies in your user's browsers.
Rather than blacklisting entire ranges of browsers based on “ of their browser.
This detect will return tests for the File API specification Tests for objects specific to the File API W3C specification without being redundant (don't bother testing for Blob since it is assumed to be the File object's prototype.)Tests for lossy, non-alpha webp support.