The Seven Parts of "HTML 5 Fundamentals"
- Posted: Mar 19, 2014 at 6:00 AM
- 21,000 Views
- 7 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
It's Web Wednesday and today we're going to take a step back and share a series by David Giard, who's going to give us a fundamental look at HTML5. Oh, I know YOU don't need this, but you might have a "friend" who does (cough... like me... cough...).
Read this series of articles to learn more about HTML5 and CSS3
HTML5 IS BIG
When I think of HTML5, I’m reminded of a quote about space by one of my favourite authors –Douglas Adams. “Space,” says Adams, “is big. Really big. I mean, you may think it’s a long way down to the chemist’s but that’s just peanuts to space.” And the reason this quote reminds me of HTML5 is because HTML 5 is big. Really big. I mean you may think it’s a long way… Well, you get the idea.
HTML5 is a set of guidelines released by the World Wide Web Consortium (the “W3C” for short) with input from the most popular browser manufacturers, such as Microsoft, Google, the Mozilla Foundation, and Apple.
The browser manufacturers are implementing the HTML5 guidelines at their own pace and in their own order. Due to the enormous scope of HTML5 and the rate at which users tend to upgrade to new browsers, it is unlikely that HTML5 will be on all computers for another decade. Does this mean that HTML5 is irrelevant today? Of course not! Each browser manufacturer is working furiously to implement new features into their browser and encouraging users to upgrade to the latest browser.
You as a developer can start taking advantages of these features today. The challenge, of course, is to build a web application that will use features of new browsers, but still be useable if a user connects with an older browser that does not support the new features. This backwards compatibility is known as “graceful degradation”, meaning that your application downgrades itself gracefully rather than crashing when it encounters a degraded browser. We will talk about ways of making your pages and applications degrade gracefully throughout this paper.
The W3C had several goals when defining HTML5...
NOTE: If you are unfamiliar with Cascading Style Sheets, please check out my earlier article on the basics of CSS.
Cascading Style Sheets (CSS) have been around for years. They contain styling information to apply to a web page and they are a recommended way to separate content from layout. The Worldwide Web Consortium (W3C) released a new set of CSS recommendations – known as “CSS3” – at about the same time they released the HTML3 recommendations, so these two specification sets are often spoken of together. CSS3 adds a number of new and useful selectors, selector filters, and styles to provide more flexibility in styling web pages.
TEXT SHADOWS ...
ROUNDED CORNERS ...
In this article, we covered a few of the new styles introduced in CSS3. In the next article, we will demonstrate a few more CSS3 features.
DETECTING BROWSER CAPABILITIES
Not every browser supports every new API. If you attempt to call an API not supported by the current, browser, the browser is likely to throw an exception, which could be a bad experience for your users. For Internet apps, it’s best to test if a feature is supported before calling it. Ideally, you should find an alternate way to provide similar functionality for unsupported browsers. At a minimum, though, your application should not crash.
SELECTING ELEMENTS ...
“DATA DASH” ATTRIBUTES ...
WEB STORAGE ...
In this series, I introduced some of the concepts and features of HTML5 and CSS3.
Once you've read his series, you might not (okay, will not) be an HTML5 ninja, but you'll be on the road to better knowing what you don't know, which is a road that can lead to ninja'ness...
Logo Credit: http://www.w3.org/html/logo/