Getting Started: Transitioning to HTML5 - HTML5 Mastery: Semantics, Standards, and Styling - page 25

// Handle lack of audio element support on the page
}
__________
3 If you want to know more about creating custom methods of detecting HTML5 features, check
out Mark Pilgram's excellent summary at http://diveintohtml5.org/detect.html .
Note Paul Irish ( http://paulirish.com ) is a lead developer on the Modern-
izr project, as well as a project called the HTML5 Boilerplate ( ht-
tp://html5boilerplate.com ) , which is worth checking out as well. The Boil-
erplate provides a default bare-bones starting template for HTML5 web projects. It in-
cludes the Modernizr and jQuery JavaScript libraries, as well as a default web page
structure and attached CSS style sheet.
Web browser developer tools
Each web browser uses software known as a layout engine to parse HTML and CSS and
render it on-screen. Unsurprisingly, these are often different for each (though Google
Chrome and Apple's Safari both use WebKit), which explains the differences in support
of HTML5 features, even among the most recent releases of different web browsers.
Since they are different, it's good to have a solid in-browser developer tool in order to
explore and manipulate the HTML/CSS. Each browser has a set of tools for aiding web
development in this regard. Typically, these tools, when enabled, allow content on the
page to be right-clicked, and an “Inspect Element” or similar option will be present in
the contextual menu. Inspecting the HTML element will reveal its structure and CSS
styling, which can be explored and manipulated (nonpermanently) in the browser. These
tools also feature some sort of “console” where JavaScript code can log commands us-
ing the code console.log("message"); or similar. See Table 1-3 for a list of ma-
jor browser's respective layout engines and developer tools.