• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Why Embrace "Html5"?

Why Embrace "Html5"?



If you're still on the fence about HTML5, this presentation covers how we got here, and why you should embrace HTML5 now.

If you're still on the fence about HTML5, this presentation covers how we got here, and why you should embrace HTML5 now.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • MS Internet Explorer team has does testing to ensure HTML5 doctype does not throw IE into quirks mode.Safari and Mozilla have also done testing of their own

Why Embrace "Html5"? Why Embrace "Html5"? Presentation Transcript

  • Why Embrace “HTML5”?
  • How We Got Here
    In 1999, a website that included images and an eye-catching design was considered “top of the line”
    2004 Web Hypertext Application Technology Working Group (WHATWG) was formed
    WHATWG felt W3c was ignoring the needs of users and browsers makers by focusing on XHTML2
    June 2009 W3C abandons work on XHTML2
  • What “HTML5” Is Not
    Not a reformulation of previous versions of the language
    XHTML 1.0 was basically HTML 4 with strict XML syntax.
    Both HTML4 and XHTML 1.0 are still in general use
    "HTML5" as we know it is steadily gaining headway daily
  • What “Html5” Is
    “HTML5” includes all valid elements from both HTML 4 and XHTML 1.0
    Because of this, it can be said that all websites are currently using “HTML5”
    Designed with some primary principles in mind to ensure it works on just about every platform
    Compatible with older browsers
    Capable of handling errors gracefully
  • What “Html5” Is
    Redefinitions of existing markup elements, and new elements that allow web designers to be more expressive in the semantics of their markup
    Any new form elements not understood or supported by older browsers automatically revert to what the browser can support, in most cases, input type=“text”
  • How HTML5 Was Designed
    The design principles used are summed up on the W3C’s HTML Design Principles page http://www.w3.org/TR/html-design-principles/
  • A Tale of Two Specifications
    WHATWG Spec http://www.whatwg.org/specs/web-apps/current-work/multipage/
    W3C Markup only Spec http://dev.w3.org/html5/markup/
    Two specifications? Should I be worried?
    No. There are only subtle differences between the two.
  • What’s The Difference?
    The WHATWG spec is a little more informal and experimental
    The W3c Spec is
    more formal, and based largely on work done in WHATWG spec
    what browser manufacturers follow when they implement new functionality
    The HTML5 spec has recently been renamed by WHATWG to "HTML" (dropping the "5")
  • A New Standard
    The newly renamed “HTML” specification is now called a "living standard"
    Meaning that it will be in constant development
    Will no longer be referred to using the incrementing numbers
  • Why Embrace It?
    HTML is forward thinking
    New HTML Form elements can validate themselves (client side)
    Form Elements not understood, or supported by browsers automatically revert to input type=“text”
    Developers can add additional validation if this happens
    Richer more meaningful semantics in markup
  • What About Older Browsers, IE?
    There are a number of excellent polyfills, or polyfillers out that enhance browser capabilities to allow them to work with these new elements
    One example, Modernizr-1.7.js, detects what features your browser does/doesn’t support and adds appropriate classes to the corresponding HTML elements that allow designers to easily target them
  • Is It Ready For Primetime?
    Yes! Some common reasons people give for not using it are:
    “It’s not a W3C Recommendation”
    Neither is CSS2 or CSS 2.1
    Should we stop using CSS to style our pages and content since it’s not a recommendation? No. We use it anyway.
    “But it’s not stable”
    Yes it is. It includes all valid elements from both HTML 4 and XHTML 1.0
    Both of these are stable so HTML5 is stable
  • Is It Ready For Primetime?
    “It’s too young”
    HTML5 as we know it now, is almost 4 years old
    It’s components
    HTML4 (14 yrs old) became a recommendation in December of 1997
    XHTML 1.0 (11 yrs old) became a recommendation in January 2000
    “It’s not fully supported in all browsers”
    Again, neither is CSS but we use it
    HTML5 was designed to degrade gracefully
  • Is It Ready For Primetime?
    “It’s not supported by IE6.”
    That’s where the polyfills mentioned earlier come in
    With a judicious use of polyfills, plus current markup techniques, your webpage will be able to give the user the best experience their browser / device of choice can support.
  • So, Who’s Using “HTML5”?
    New Doctype only
    … and others
  • So, Who’s Using “HTML5”?
    New Doctype and New Markup
    … and others
  • Isn’t It Time You Embraced HTML?