Thursday, October 6, 2011

modernizrModernizr.js is a little library that will help "modernize" old browsers.

As an example, let's say you create a new ASP.NET MVC 3 application with the "Use HTML 5 semantic markup" checkbox selected. If you peek into the layout view for the app, you'll find the following markup:

    <ul id="menu">
        <li>@Html.ActionLink("Home", "Index", "Home")</li>
        <li>@Html.ActionLink("About", "About", "Home")</li>

The nav element represents a section with navigation links, and is a new element in the HTML 5 spec. The idea is that using nav gives more meaning to the page, and allows user agents like screen readers to identify navigation information (contrast nav against using a regular div element as the container  - a div carries relatively no semantic value by itself).

There is a problem, however. Older versions of Internet Explorer (anything before version 9) do not recognize the nav element. IE refuses to apply style rules to unidentified elements, and will also not allow unidentified elements to have children in the DOM. If you have to support older versions of IE this will sound like a dire situation, but it turns out there is an easy solution.

HTML5 Shiv

You can "register" elements in IE using document.createElement. For example…


... is all you need to do for IE to apply style rules to <foo> elements, and construct them appropriately in the DOM. Years ago Remy Sharp created the html5shiv project, which was the first library to essentially execute createElement for all of the new HTML 5 elements, including nav, article, footer, header, etc. html5shiv then allows IE to recognize all HTML 5 elements. 

Modernizr also "registers" all HTML 5 elements, meaning the HTML 5 MVC web application you build will work just fine on older versions of IE (as long as you leave Modernizer in your layout view). One note: you'll want to keep the script tag for Modernizr inside the <head> element. All the calls to createElement for new elements must happen before IE reaches the <body> tag.

Enabling HTML 5 elements is just one of the features Modernizr provides. In future posts we'll look at Modernizr's ability to detect features, and inject fallback scripts.

gravatar Jason Jarrett Thursday, October 6, 2011
Nice overview.

I started to write the following question but stopped and looked it up myself - Case anyone else had the question...

Question - you mention the html5shiv project and you say it does what modernizer is trying to accomplish (but it started earlier?). Do you know why you should chose one over the other.

What a quick search found:
Scott Thursday, October 6, 2011
@Jason: Modernizr will do some additional things that we will look at next week.
magellings Friday, October 7, 2011
Sweet! I did not know Modernizr did this. Thanks for sharing.
gravatar Daniel Wednesday, October 12, 2011
I've looked at Modernizr and its docu but what it does is still not clear to me:
It just detects (missing) features or it detects (missing) features AND adds them to allow the developer to use them in non compliant browsers?
gravatar tatab&#225;nya nyelviskola Wednesday, October 12, 2011
same questions as Daniell...
gravatar scott Wednesday, October 12, 2011
@Daniel, @tatabanya: By default Modernizr is only detecting features - it doesn't try to fill them in unless you write some more code and pull in additional scripts. This is what we will look at next week.
gravatar tatab&#225;nya nyelviskola Saturday, October 15, 2011
@scott: thank you
gravatar John Puddifoot Tuesday, October 18, 2011
Hi Scott, very useful, thanks - but surely no-one is still using IE5! :p
Comments are closed.
Pluralsight Courses
What JavaScript Developers Should Know About ECMAScript 2015
The Podcast!