Modernizr

The long wait is over—Modernizr 2 is here! Modernizr 2 takes feature detection to the next level, enabling a powerful new approach to building great websites and applications that elegantly respond and adapt to the user’s environment. What’s new: ... [More] Media Query testing: Modernizr.mq('only all and (max-width: 600px)') // true Conditional resource loading via Modernizr.load() — powered by yepnope.js; Vendor prefix detection Modernizr.prefixed('transform') // 'WebkitTransform' A whole new set of extensibility methods, so its easy to augment the Modernizr tests with your own. A brand new site! …with the custom build tool baked right in; …and a completely revamped, much more detailed Documentation page. Modernizr 2 now contains 40 feature detection tests, but only the development version will come bundled with all of them. When you are ready to get a compressed and minified production build, simply go to the Download page and pick and choose only the tests and features that you need. This way, we ensure that your production build will have the absolute smallest footprint and fastest execution time possible. A little tip: when you make a custom build, your URL will be adjusted to reflect your choices exactly. Bookmark it after building in case you ever need to go back and adjust your settings! We know you might need to detect more than what’s available in the Modernizr core. Keep an eye on our feature-detects folder for the best-of-breed detections for everything. Want to learn how to do conditional resource loading with Modernizr.load()? Our new documentation comes with a great Modernizr.load tutorial that takes you through the basics and gets you started. Alternatively, you could check out our site’s own modernizr.com-custom.js for some inspiration. We’d love to get your feedback on the new Modernizr, the new site and our new documentation and resources pages. Let us know via Twitter, especially if you come across a bug somewhere—things are still a little rough around the edges here and there, but we figured you’d prefer to have Modernizr 2 sooner rather than later. A huge thanks goes out to all of our contributors who provided code for additional tests, helped us with debugging and getting our detection algorithms right, and so much more. Additionally, special thanks go out to Simon a.k.a. Simurai, for crafting some fancy CSS3 buttons for us, Ryan Seddon for integration work, and Aaron Gustafson for making sure our ARIA roles were top notch. — Team Modernizr (Faruk Ateş, Paul Irish and Alex Sexton) [Less]

The long wait is over—Modernizr 2 is here! Modernizr 2 takes feature detection to the next level, enabling a powerful new approach to building great websites and applications that elegantly respond and adapt to the user’s environment. What’s new: ... [More] Media Query testing: Modernizr.mq('only all and (max-width: 600px)') // true Conditional resource loading via Modernizr.load() — powered by yepnope.js; Vendor prefix detection Modernizr.prefixed('transform') // 'WebkitTransform' A whole new set of extensibility methods, so its easy to augment the Modernizr tests with your own. A brand new site! …with the custom build tool baked right in; …and a completely revamped, much more detailed Documentation page. Modernizr 2 now contains 40 feature detection tests, but only the development version will come bundled with all of them. When you are ready to get a compressed and minified production build, simply go to the Download page and pick and choose only the tests and features that you need. This way, we ensure that your production build will have the absolute smallest footprint and fastest execution time possible. A little tip: when you make a custom build, your URL will be adjusted to reflect your choices exactly. Bookmark it after building in case you ever need to go back and adjust your settings! We know you might need to detect more than what’s available in the Modernizr core. Keep an eye on our feature-detects folder for the best-of-breed detections for everything. Want to learn how to do conditional resource loading with Modernizr.load()? Our new documentation comes with a great Modernizr.load tutorial that takes you through the basics and gets you started. Alternatively, you could check out our site’s own modernizr.com-custom.js for some inspiration. We’d love to get your feedback on the new Modernizr, the new site and our new documentation and resources pages. Let us know via Twitter, especially if you come across a bug somewhere—things are still a little rough around the edges here and there, but we figured you’d prefer to have Modernizr 2 sooner rather than later. A huge thanks goes out to all of our contributors who provided code for additional tests, helped us with debugging and getting our detection algorithms right, and so much more. Additionally, special thanks go out to Simon a.k.a. Simurai, for crafting some fancy CSS3 buttons for us, Ryan Seddon for integration work, and Aaron Gustafson for making sure our ARIA roles were top notch. — Team Modernizr (Faruk Ateş, Paul Irish and Alex Sexton) [Less]

We put 1.7 live some time ago but never got around to publishing a changelog. Since people have been asking, below are the core changes. For an exact changelog, see the commit log on github between 1.6 and 1.7. At the heart of 1.7 are the following ... [More] major changes: A weaker, less crash-prone test for WebGL A fix for @font-face in certain browsers Faster Drag & Drop test Updated IE Print Protector for better speed and reliability One less content reflow due to better className setting Beyond these main changes, 1.7 fixes lots of small bugs like tiny memory leaks and the occasional false returns in certain browsers.  A small update on the Modernizr 2 front: we’re getting very close to releasing it, so if you encounter any major bugs using either 1.7 or the 2.0 beta builder, please report them on github as soon as possible. We already have a lot of issues and features pushed to our planned 2.1 release, but would love to make sure that the 2.0 release is the absolute best version of Modernizr yet. [Less]

We put 1.7 live some time ago but never got around to publishing a changelog. Since people have been asking, below are the core changes. For an exact changelog, see the commit log on github between 1.6 and 1.7. At the heart of 1.7 are the ... [More] following major changes: A weaker, less crash-prone test for WebGL A fix for @font-face in certain browsers Faster Drag & Drop test Updated IE Print Protector for better speed and reliability One less content reflow due to better className setting Beyond these main changes, 1.7 fixes lots of small bugs like tiny memory leaks and the occasional false returns in certain browsers.  A small update on the Modernizr 2 front: we’re getting very close to releasing it, so if you encounter any major bugs using either 1.7 or the 2.0 beta builder, please report them on github as soon as possible. We already have a lot of issues and features pushed to our planned 2.1 release, but would love to make sure that the 2.0 release is the absolute best version of Modernizr yet. [Less]

A brand new year, a brand new Modernizr! What’s new in 2011: A new addition to our team, Alex Sexton We’re introducing a new builder, so you can customize your download of Modernizr to suit your needs A first beta release of Modernizr 2! But ... [More] first, let’s quickly recap what happened in 2010, which was a fantastic year for Modernizr. We had the major 1.5 release really hitting it big, the incremental 1.6 and small site update, and finishing off the year by winning the Open Source Application of the Year category at the 2010 .net Awards. We’d like to thank all of our contributors for their hard work making this such a great open source application. But looking forward to 2011, we have so much more in store for you that 2010 will appear mundane by comparison. We’re kicking it off with some pretty exciting news right away. First, we’ve expanded our team to include Alex Sexton. Due to this addition we’ve also formalized our individual roles in the Modernizr Team, as such: Faruk Ateş: Project Lead Paul Irish: Lead Developer Alex Sexton: Developer Second, Alex has been working on something we’ve all wanted since the day Modernizr was released, and that’s the ability to customize your own download of the library to only include the tests that you want. This functionality was kept out for simplicity’s sake originally, but has become sorely needed since then. Thanks to Alex, Modernizr 2 will have this functionality—and even better than originally imagined, too. The original plan involved a server-side compiler, but Alex’s fine work, unofficially named Modulizr, has brought us an all-client side builder. Best of all: you can start playing around with it right now because today we’re launching the first beta of Modernizr 2! This very first beta introduces the customizability of Modernizr 2, allowing you to pick and choose the tests you want in your production-optimized download. We’d love to get your feedback through use of the (beta) builder, so please head on over the beta page and configure your preferred download of Modernizr. Looking beyond the beta, our road map for Modernizr already includes specifics for a 2.1 release. We’re committed to getting Modernizr 2 finished and out in the open as soon as possible, and will have more announcements for you in the near future. For now, enjoy the beta and have a fantastic 2011! — Team Modernizr [Less]

A brand new year, a brand new Modernizr! What’s new in 2011: A new addition to our team, Alex Sexton We’re introducing a new builder, so you can customize your download of Modernizr to suit your needs A first beta release of Modernizr 2! ... [More] But first, let’s quickly recap what happened in 2010, which was a fantastic year for Modernizr. We had the major 1.5 release really hitting it big, the incremental 1.6 and small site update, and finishing off the year by winning the Open Source Application of the Year category at the 2010 .net Awards. We’d like to thank all of our contributors for their hard work making this such a great open source application. But looking forward to 2011, we have so much more in store for you that 2010 will appear mundane by comparison. We’re kicking it off with some pretty exciting news right away. First, we’ve expanded our team to include Alex Sexton. Due to this addition we’ve also formalized our individual roles in the Modernizr Team, as such: Faruk Ateş: Project Lead Paul Irish: Lead Developer Alex Sexton: Developer Second, Alex has been working on something we’ve all wanted since the day Modernizr was released, and that’s the ability to customize your own download of the library to only include the tests that you want. This functionality was kept out for simplicity’s sake originally, but has become sorely needed since then. Thanks to Alex, Modernizr 2 will have this functionality—and even better than originally imagined, too. The original plan involved a server-side compiler, but Alex’s fine work, unofficially named Modulizr, has brought us an all-client side builder. Best of all: you can start playing around with it right now because today we’re launching the first beta of Modernizr 2! This very first beta introduces the customizability of Modernizr 2, allowing you to pick and choose the tests you want in your production-optimized download. We’d love to get your feedback through use of the (beta) builder, so please head on over the beta page and configure your preferred download of Modernizr. Looking beyond the beta, our road map for Modernizr already includes specifics for a 2.1 release. We’re committed to getting Modernizr 2 finished and out in the open as soon as possible, and will have more announcements for you in the near future. For now, enjoy the beta and have a fantastic 2011! — Team Modernizr [Less]

Today we’re announcing the new Modernizr 1.6, an interim release in the run-up to the upcoming Modernizr 2.0—a release slated for later this year which will take the library to the next level. Before we get into what’s new in 1.6, we want to quickly ... [More] thank Darcy Clarke for his quick but handy CSS tweaks to our site, cleaning things up a little and improving legibility. Much like today’s 1.6 release, these changes to the site reflect some of what’s coming up in the new 2.0 release and the “2.0” website, if you will. As said, Modernizr 1.6 is an interim release and closes some important issues while adding a few new detections. Besides bringing it down to a mere 3.8Kb minified and gzipped, the biggest improvement is a completely revised @font-face test, which fixes the FOUT—Flash Of Unstyled Text—which was a somewhat common issue when combining Modernizr with Typekit. We’ve also added support for WebGL, Touch events, Flexible Box Layouts and Inline SVG. Additionally, several existing tests have been improved to better support newer browser releases, as well as fix some minor bugs. There are some important changes in 1.6: first, the Modernizr.websqldatabase test has been simplified. It no longer creates a database, which solves an annoying Safari pop-up issue and stops Modernizr from littering the web with databases, but it comes at somewhat of a cost: Chrome in Incognito mode will now false-positive on this test. The extended test remains commented-out in the non-minified source, for those who need it to be exact. Second, we’ve deprecated two properties: Modernizr.crosswindowmessaging and Modernizr.historymanagement. Going forward, these two properties are simply: Modernizr.postmessage Modernizr.history Simpler, cleaner, and they now match the actual DOM property they’re testing for. Keep in mind that, as with other tests, the Modernizr property is all-lowercase but the actual DOM property is window.postMessage. Lastly, we’ve put the oft-requested CSS text-shadow test in this release. It still false-positives in Firefox 3.0, but we think web designers are okay with that these days. We hope you enjoy this new release, and stay tuned for big changes with the upcoming Modernizr 2.0! Download the new Modernizr 1.6 from the front page [Less]

Today we’re announcing the new Modernizr 1.6, an interim release in the run-up to the upcoming Modernizr 2.0—a release slated for later this year which will take the library to the next level. Before we get into what’s new in 1.6, we want to ... [More] quickly thank Darcy Clarke for his quick but handy CSS tweaks to our site, cleaning things up a little and improving legibility. Much like today’s 1.6 release, these changes to the site reflect some of what’s coming up in the new 2.0 release and the “2.0” website, if you will. As said, Modernizr 1.6 is an interim release and closes some important issues while adding a few new detections. Besides bringing it down to a mere 3.8Kb minified and gzipped, the biggest improvement is a completely revised @font-face test, which fixes the FOUT—Flash Of Unstyled Text—which was a somewhat common issue when combining Modernizr with Typekit. We’ve also added support for WebGL, Touch events, Flexible Box Layouts and Inline SVG. Additionally, several existing tests have been improved to better support newer browser releases, as well as fix some minor bugs. There are some important changes in 1.6: first, the Modernizr.websqldatabase test has been simplified. It no longer creates a database, which solves an annoying Safari pop-up issue and stops Modernizr from littering the web with databases, but it comes at somewhat of a cost: Chrome in Incognito mode will now false-positive on this test. The extended test remains commented-out in the non-minified source, for those who need it to be exact. Second, we’ve deprecated two properties: Modernizr.crosswindowmessaging and Modernizr.historymanagement. Going forward, these two properties are simply: Modernizr.postmessage Modernizr.history Simpler, cleaner, and they now match the actual DOM property they’re testing for. Keep in mind that, as with other tests, the Modernizr property is all-lowercase but the actual DOM property is window.postMessage. Lastly, we’ve put the oft-requested CSS text-shadow test in this release. It still false-positives in Firefox 3.0, but we think web designers are okay with that these days. We hope you enjoy this new release, and stay tuned for big changes with the upcoming Modernizr 2.0! Download the new Modernizr 1.6 from the front page [Less]

We're proud and pleased to announce the immediate release of Modernizr 1.5! Rather than an incremental upgrade, we've opted to shift into a higher gear and add the full shebang of what we've been working on. Here's a list of new things we detect: ... [More] SVG! Including SVG Clipping Paths and SMIL Web SQL Database IndexedDB Web Sockets hashchange event History and Session Management HTML5 Drag and Drop Cross-document Messaging Additionally, IE can now print HTML5 elements (courtesy of @jon_neal's print protector), IE9 should be fully supported (let us know if you discover inconsistencies), and we also support more browsers: older Safari versions, Nokia and Blackberry mobile browsers, and Konqueror via the -khtml- prefix. Detection of Opera's CSS3 support for transitions and transforms was fixed, as well. A few big things have kept us busy preparing a good release. Flash detection (Flash Blockers included) became a hot topic and we really wanted to include it, but at the time no reliable or complete mechanism was available. We wanted to include (and still recommend) Mark Pilgrim's excellent Flash Block Detector but decided that it was too large a codebase to include in the default release of Modernizr—especially given the modular Modernizr 2 plans on the horizon—and so Flash detection is out for now. Then came the discovery that Google Chrome implemented Touch events even on the desktop (why, Google, why?) paired with the regrettable fact that Palm's WebOS browser doesn't support common Touch events at all. For a browser that only exists on touch-based devices, this was too critical an issue for us to ignore. So Touch testing went out again, too. We have many more features we'd like to include; please visit the Github issue tracker to review all the additional tests. For developers, contributors and people looking to learn from Modernizr we now have a set of unit tests available on the Github repository, courtesy of Paul. These help prevent errors and inconsistencies from finding their way into the source code, making Modernizr more robust and reliable. The unit tests also include a second part, which pulls the data tables in from Find Me By IP and creates a feature parity overview for all the browsers. Along with the 1.5 release comes a license upgrade: Modernizr is now dual-licensed under BSD and MIT. Thanks for all the input and code to miketaylr, fearphage, kangax, richbradshaw, @itpastorn, @jon_neal, dshaw, itrelease, mathiasbynens, airportyh, jeffsmith, rjcoelho, lucideer, peol and mislav. The high quality of this release wouldn't be possible with input from experts like these. We hope you enjoy the hard work we've all put into it, but we'd love to hear your feedback on Modernizr 1.5's new changes, so let us know via Twitter what you think! [Less]

We're proud and pleased to announce the immediate release of Modernizr 1.5! Rather than an incremental upgrade, we've opted to shift into a higher gear and add the full shebang of what we've been working on. Here's a list of new things we detect: ... [More] SVG! Including SVG Clipping Paths and SMIL Web SQL Database IndexedDB Web Sockets hashchange event History and Session Management HTML5 Drag and Drop Cross-document Messaging Additionally, IE can now print HTML5 elements (courtesy of @jon_neal's print protector), IE9 should be fully supported (let us know if you discover inconsistencies), and we also support more browsers: older Safari versions, Nokia and Blackberry mobile browsers, and Konqueror via the -khtml- prefix. Detection of Opera's CSS3 support for transitions and transforms was fixed, as well. A few big things have kept us busy preparing a good release. Flash detection (Flash Blockers included) became a hot topic and we really wanted to include it, but at the time no reliable or complete mechanism was available. We wanted to include (and still recommend) Mark Pilgrim's excellent Flash Block Detector but decided that it was too large a codebase to include in the default release of Modernizr—especially given the modular Modernizr 2 plans on the horizon—and so Flash detection is out for now. Then came the discovery that Google Chrome implemented Touch events even on the desktop (why, Google, why?) paired with the regrettable fact that Palm's WebOS browser doesn't support common Touch events at all. For a browser that only exists on touch-based devices, this was too critical an issue for us to ignore. So Touch testing went out again, too. We have many more features we'd like to include; please visit the Github issue tracker to review all the additional tests. For developers, contributors and people looking to learn from Modernizr we now have a set of unit tests available on the Github repository, courtesy of Paul. These help prevent errors and inconsistencies from finding their way into the source code, making Modernizr more robust and reliable. The unit tests also include a second part, which pulls the data tables in from Find Me By IP and creates a feature parity overview for all the browsers. Along with the 1.5 release comes a license upgrade: Modernizr is now dual-licensed under BSD and MIT. Thanks for all the input and code to miketaylr, fearphage, kangax, richbradshaw, @itpastorn, @jon_neal, dshaw, itrelease, mathiasbynens, airportyh, jeffsmith, rjcoelho, lucideer, peol and mislav. The high quality of this release wouldn't be possible with input from experts like these. We hope you enjoy the hard work we've all put into it, but we'd love to hear your feedback on Modernizr 1.5's new changes, so let us know via Twitter what you think! [Less]