HTML5--The 30,000' View (A fast-paced overview of HTML5)

Thanks to the Sponsors! • Twilio (event venue) Twilio’s software allows your web application to easily make and receive phone calls and SMS text messages using a simple web service API. Kaazing (event pizza and drinks) Kaazing WebSocket Gateway features patent-pending, ultra high-performance HTML5 WebSocket Acceleration™ technology that enables companies to quickly deliver massively scalable, real-time web applications • Marakana (event organization) Marakana provides cutting-edge open source software training in San Francisco, New York, Toronto, and on- demand corporate training 2 Copyright © 2010 - Kaazing Corporation. All rights reserved.

About Peter Lubbers • Director of Documentation and Training, Kaazing • Co-Founder San Francisco HTML5 User Group http://www.sfhtml5.org/ • Co-author Pro HTML5 Programming o Alpha Release: www.prohtml5.com o Special 50% Off Coupon Code: APRESSPROHTML5WR (expires May 31st) • Ultra Distance Runner • Twitter: @peterlubbers 3 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Verbatim “The world is moving to HTML5” —Steve Jobs, Apple “The Web has not seen this level of transformation, this level of acceleration, in the past ten years… we're betting big on HTML5” —Vic Gundotra, VP of Engineering, Google “In a nutshell, we love HTML5, we love it so much we want it to actually work. —Dean Hachamovitch, General Manager for Internet Explorer, Microsoft “I had no idea there was so much HTML5 already in play” 5 —Tim O’Reilly Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Standards Bodies • Web Hypertext Application Technology Working Group (WHATWG) o Founded in 2004 (by individuals working for browser vendors Apple, Mozilla, Google, and Opera) o Develops HTML and APIs for web application development o Unofficial and open collaboration of browser vendors and interested parties • World Wide Web Consortium (W3C) o Created draft of HTML5 in 2008 • Internet Engineering Task Force (IETF) o Protocols (HTTP, WebSocket) 12 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Specifications • WHATWG o http://www.whatwg.org/specs/web-apps/current-work/ • W3C o http://dev.w3.org/html5/spec/Overview.html • IETF (WebSocket specification) o http://tools.ietf.org/html/draft-hixie- thewebsocketprotocol 13 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Is This HTML5? • Many pieces of the HTML5 effort (for example, Local Storage, WebSocket, and Geolocation) were originally part of the HTML5 specification • Moved to a separate standards document to keep the specification focused • Industry still refers to the original set of features, including Web Sockets, as "HTML5“ • See: http://www.whatwg.org/specs/web-apps/current- work/multipage/introduction.html#is-this-html5? 14 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Design Principal #1 Compatibility • Pave the cow paths • Degrade gracefully • Research common behavior; solve real problems • Support existing content • Evolution not revolution • Don’t reinvent the wheel (or at least make a 16 better one!) Copyright © 2010 - Kaazing Corporation. All rights reserved.

Design Principal #2 Utility • Priority of Constituencies: o When in doubt… value users over authors, over implementers (browsers), over specifiers (W3C/WHATWG), over theoretical purity. • Secure by design • DOM consistency (HTML5 and XHTML5) • Separation of presentation and content 17 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Presentation vs. Content • HTML5 strives to separate content from presentation where possible (use CSS) • Most of the presentational features from earlier versions of HTML are no longer supported • This was already in the works (HTML4 Transitional, XHTML1.1) • Problems with presentational markup: o Poor accessibility o Unnecessary complexity 18 o Larger document size Copyright © 2010 - Kaazing Corporation. All rights reserved.

Design Principal #3 Interoperability • Specify well-defined behavior o Specific instead of vague • Handle errors well o Improved and ambitious error handling plans o Prefer graceful error recovery to hard failure • Avoid needless complexity o Simple is better 19 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Simple is Better • Simplify wherever possible • Examples: o Native browser ability instead of complex JavaScript code o New doctype o Character set o HTML5 APIs 20 Copyright © 2010 - Kaazing Corporation. All rights reserved.

• HTML4/XHTML HTML 4.01 Strict Simplified Doctype • HTML 4.01 Transitional • HTML 4.01 Frameset • XHTML 1.0 Strict • XHTML 1.0 Transitional • XHTML 1.0 Frameset • XHTML 1.1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> HTML5 21 <!DOCTYPE html> Copyright © 2010 - Kaazing Corporation. All rights reserved.

More Detail (Where Needed) • HTML5 is more detailed than previous specs to avoid misinterpretation • Aim to define things thoroughly, especially web applications • ~900 Pages spread over multiple specifications 23 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Design Principal #4 Universal Access • Support for all world languages o For example, <ruby> (Ruby annotations, used in East Asian typography) • Accessibility o Support users with disabilities o Web Accessibility Initiative (WAI) Accessible Rich Internet Applications (ARIA) o WAI-ARIA roles can be added today 24 o Supported by screen readers Copyright © 2010 - Kaazing Corporation. All rights reserved.

Plugin-Free Paradigm • HTML5 provides native support for many features that were only possible with plugins or complex hacks o Plugins may not be installed o Plugins can be disabled or blocked (iPad does not ship with Flash plugin) o Plugins are a separate attack vector o Plugins are difficult to integrate with the rest of an HTML document (plugin boundaries, clipping, and transparency issues) o Plugins are crash prone 25 Copyright © 2010 - Kaazing Corporation. All rights reserved.

New HTML5 Tags <article> <aside> <audio> <canvas> <command> <datalist> <details> <dialog> <embed> <figure> <footer> <header> <hgroup> <keygen> <mark> <meter> <nav> <output> <ruby> <rt> <rp> <section> <source> <video> 29 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Content Types • Metadata content o Elements—commonly found in the head section— that set up the presentation or behavior of the rest of the document, for example script, style, title • Flow content o Elements used in the body of documents and applications, for example form, h1, small • Sectioning content o Elements that define sections in the document, for example article, aside, title 32 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Content Types (Continued) • Heading content o Section headers, for example h1, h2, hgroup • Phrasing content o Text and text markup elements, for example mark, kbd, sub, sup, b • Embedded content o Content that imports other resources into the document, for example audio, video, canvas, iframe • Interactive content o Content that users interact with, for example 33 audio or video controls, button, textarea Copyright © 2010 - Kaazing Corporation. All rights reserved.

Anatomy of an HTML5 Page HTML code (head section) <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>HTML 5</title> <link rel="stylesheet" href="html5.css"> </head> 35 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Anatomy of an HTML5 Page HTML code body section (part 1) <body> <header> <h1>Header</h1> </header> <div id="container"> <nav> <h3>Nav</h3> </nav> 36 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Anatomy of an HTML5 Page HTML code body section (part 2) <section> <article> <header> <h1>Article Header</h1> </header> <footer> <h2>Article Footer</h2> </footer> </article> </section> 37 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Anatomy of an HTML5 Page HTML code body section (part 3) <aside> <h3>Aside</h3> </aside> <footer> <h2>Footer</h2> </footer> </div> </body> </html> 38 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 and CSS Level 3 • CSS level 2 (W3C) o published as a Recommendation1998 o Candidate Recommendation 2007 • CSS Level 3 (W3C) o Like HTML5, under development o Modularized with sub-specifications for easier browser uptake (transformation, animation, transition) • Some CSS Level 3 examples: o http://www.zurb.com/playground/ o http://www.zachstronaut.com/ 42 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Forms • Formerly called Web Forms 2.0 • Native functionality (no scripting for validation) means less coding, for example: Regular expression for a valid e-mail address: (?:[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:.[a-z0- 9!#$%&'*+/=?^_`{|}~-]+)*|"(?:[x01- x08x0bx0cx0e-x1fx21x23-x5bx5d- x7f]|[x01-x09x0bx0cx0e- x7f])*")@(?:(?:[a-z0-9](?:[a-z0-9-]*[a-z0- 9])?.)+[a-z0-9](?:[a-z0-9-]*[a-z0- 9])?|[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0- 9]?).){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0- 9]?|[a-z0-9-]*[a-z0-9]:(?:[x01- x08x0bx0cx0e-x1fx21-x5ax53- x7f]|[x01-x09x0bx0cx0e-x7f])+)]) 44 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Forms • New form functionality: o Date and color pickers o Search, e-mail, web address input types o Validation o Spin boxes and Sliders o More • Backward compatible • Features degrade gracefully (unknown input types are treated as text-type) input 45 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 APIs • Canvas and SVG • Audio and Video • WebSocket • Server-Sent Events • Communication o Cross Document Messaging o XMLHttpRequest Level 2 • Web Workers • Geolocation • Web Storage 50 Copyright © 2010 - Kaazing Corporation. All rights reserved.

About Canvas and SVG • Previously possible with Flash, VML, Silverlight • Very complex to do in JavaScript without plugins (for example, rounded corners or diagonal lines) • Provide native drawing functionality on the Web • Completely integrated into HTML5 documents (part of DOM) • Can be styled with CSS 52 • Can be controlled with JavaScript Copyright © 2010 - Kaazing Corporation. All rights reserved.

Canvas vs. SVG • Not a matter of good or bad • Both can be used and they can also be combined Canvas SVG Low level High level Immediate mode Retained mode Fixed size Scalable Best for keyboard-based apps Best for mouse-based apps Animation (no object storage) Medium animation Pixels XML object model No interaction User interaction (hit detection, events on the tree) 53 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Canvas • HTML5 element and plugin-free 2D drawing API that enables you to dynamically generate and render o Graphics o Charts o Images o Animation • Canvas was originally introduced by Apple to be used in Mac OS X WebKit to create dashboard widgets 54 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Canvas • Canvas is a scriptable bitmap canvas (images that are drawn are final and cannot be resized • No object tree • Can be manipulated with JavaScript and styled with CSS • 2D Context • 3D Context (Web GL) 55 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for 2D Canvas • Chrome 2.0+ • Firefox 3.0+ (3.5+)* • Opera 9.6+ (10.5+)* • Safari 3.1+ (4.0+)* * Additional support for Canvas Text API 57 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for 3D Canvas (Web GL) • Chrome 5.0+ • Nightly builds of Safari • Planned for Firefox 3.7 * Additional support for Canvas Text API 58 Copyright © 2010 - Kaazing Corporation. All rights reserved.

SVG • Modularized, XML-based language for describing 2D vector and mixed vector/raster graphics • SVG has been around on the Web since 2002 (using plugins) • SVG provides high fidelity graphics at any zoom level • Until now mostly used for static content (maps, org charts, floor plans, etc.) • HTML5 now allows native SVG content in the browser (control with JavaScript, style with CSS) 60 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for SVG The percentages shown are based on combined support for all SVG modules (for example Basic, Inline, filters): • Chrome 2.0+ (58%) • Firefox 3.0 (33%) 3.6 (46%) • Opera 9.6+ (83%) • Safari 3.1 (13%) 3.2 (46%) 4.0 (58%) Note: IE 9 Will provide full support 62 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Audio and Video • New HTML5 media elements o <audio> o <video> • Control using Audio/Video API • Native support in the browser (embedded codecs) • Originally, the HTML5 specification was going to require codec support… 65 Copyright © 2010 - Kaazing Corporation. All rights reserved.

AV Containers and Codecs • Audio and Video containers: o H264 and Ogg • Audio and video codecs (algorithms used to encode and decode an audio or video stream): o Audio: AAC, MP3, Vorbis o Video: H264, MP4, Theora • Stalemate over patented/free codec inclusion • You can add multiple formats per (audio/video) element to fallback 66 Copyright © 2010 - Kaazing Corporation. All rights reserved.

About HTTP • HTTP was originally designed for document transfer • HTTP is half-duplex (traffic flows in only one direction at a time) • Hard to achieve real-time, bi-directional communication • Tons of unnecessary HTTP header information sent with each HTTP request and response and added latency 71 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Comet and Polling: Tin-Can Communication • Comet and (Reverse) Ajax o Great toilet cleaners o Bad for real-time communication o Polling and Long-Polling 72 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Example HTTP Request Headers POST /gwt/EventService HTTP/1.1 Host: gpokr.com Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1064 Safari/532.5 Referer: http://gpokr.com/gwt/7F5E66657B938E2FDE9CD39095A0E9E6.cache.html Content-Length: 134 Origin: http://gpokr.com Content-Type: text/plain; charset=utf-8 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: __utmz=247824721.1273102477.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd =(none); JSESSIONID=E7AAE0E60B01FB88D1E3799FAD5C62B3; __utma=247824721.1247485893.1273102477.1273104838.1273107686.3; __utmc=247824721; __utmb=247824721.4.10.127 73 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTTP Response Headers 200 OK Server: Apache-Coyote/1.1 Expires: Thu, 06 May 2010 01:06:51 GMT Content-Type: text/plain;charset=UTF-8 Content-Length: 303 Date: Thu, 06 May 2010 01:06:50 GMT • Total (unnecessary) HTTP request and response header information overhead: 871 bytes (example) • Overhead can be as much as 2000 bytes 74 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 WebSocket • W3C API and IETF Protocol • Full-duplex, text-based socket • Enables web pages to communicate with a remote host • Traverses firewalls, proxies, and routers seamlessly • Share port with existing HTTP content (80/443) • Cross-domain ready (leverages Cross-Origin Resource Sharing) 77 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 WebSocket • Connection established by upgrading from the HTTP protocol to the WebSocket protocol using the same TCP connection • Once upgraded, WebSocket data frames can be sent back and forth between the client and the server in full-duplex mode • Frames can be sent full-duplex, in either direction at any the same time • Each frame of data: o Starts with a 0x00 byte and End with a 0xFF byte 78 o Contains UTF-8 data in between Copyright © 2010 - Kaazing Corporation. All rights reserved.

Overheard… “Reducing kilobytes of data to 2 bytes…and reducing latency from 150ms to 50ms is far more than marginal. In fact, these two factors alone are enough to make WebSocket seriously interesting to Google.” —Ian Hickson (Google, HTML5 spec lead) 80 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Beyond WebSocket • Once you have WebSocket, you can communicate with WebSocket Servers and back- end servers and directly with message brokers • You can extend client-server protocols to the web: • XMPP, Jabber • Pub/Sub (Stomp/AMQP) • Gaming protocols • Any TCP-based protocol • Browser becomes a first-class network 81 communication citizen Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for WebSocket • Chrome 4.0+ • WebKit Nightly builds • Support planned for Firefox 3.7, Opera • Note: Full HTML4 Emulation available o Kaazing WebSocket Gateway (supports native WebSocket and provides emulation for older browsers) 83 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Server-Sent Events • Server-Sent Events (SSE) standardizes and formalizes how a continuous stream of data can be sent from a server to a browser • Effectively standardizes Comet and Reverse Ajax • EventSource API for broadcasting data from server to client 86 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for Server-Sent Events • Opera 9.0+ partial support • Development in Firefox Trunk • Note: With WebSocket support, SSE support is not as important 88 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Cross Document Messaging • Enables secure cross-origin communication across iframes, tabs, and windows (using origin security) • Defines the PostMessage API as a standard way to send messages • Provides asynchronous message passing between JavaScript contexts • HTML5 clarifies and refines domain security by introducing the concept of an origin 92 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Origin Concept • An origin is a subset of an address used for modeling trust relationships on the Web • Origins are made up of a scheme, a host, and a port—different origin: o https://www.example.com o http://www.example.com • The path is not considered in the origin value—same origin: o http://www.example.com/index.html o http://www.example.com/page2.html 93 Copyright © 2010 - Kaazing Corporation. All rights reserved.

XMLHttpRequest Level 2 • XMLHttpRequest Level 2 • XMLHttpRequest is the API that made Ajax possible • XMLHttpRequest Level 2 significantly enhances XMLHttpRequest o Progress events o Cross-origin XMLHttpRequest • XMLHttpRequest Level 2 allows for cross- origin XMLHttpRequests using Cross Origin Resource Sharing (CORS) http://www.w3.org/TR/access-control/ 96 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Web Workers • Provide background processing capabilities to web applications • Typically run on separate threads so apps can take advantage of multicore CPUs o Background number-crunchers o Background price updates from server o Search queries 100 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Geolocation • Allows users to share their location for location-aware services o Show user's position on map o Tag content (photos/sound/video) o Turn-by-turn navigation o Alert users of nearby points of interest o Social networking • Users must be allowed to opt in to location sharing 105 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Location Data • Location information consists of a pair of latitude and longitude coordinates and accuracy information o Latitude is the numerical value indicating distance north or south of the equator o Longitude is the numerical value indicating distance east or west of Greenwich, England o For Example, Lake Tahoe: Latitude: 39.17222, Longitude: -120.13778 • Coordinates are always returned in decimal format 106 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Additional Location Metadata • Depending on the device, additional meta data can be provided: o Altitude o altitudeAccuracy o Heading o Speed • If this additional metadata is not available it will be returned as a null value. 107 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Location Sources • A device can use any of the following sources: o IP address o Coordinate triangulation o Global Positioning System (GPS) o Wi-Fi with MAC addresses from RFID, Wi-Fi, and Bluetooth o GSM or CDMA cell phone IDs o User defined • Each have pros and cons 108 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Map Integration • Coordinates are not easy to decipher, easier to see on a map • Google Maps has built support for HTML5 Geolocation into its user interface (Show My Location button) 112 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for Geolocation • Firefox 3.5+ • Safari 4.0+ on iPhone • Chrome (Dev channel) • Support planned in Opera • Also available in Gears 113 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Web Storage • Web Storage a.k.a “cookies on steroids” • Three types: 1. Session Storage Area 2. Local Storage Area 3. Web SQL Database Cookies 116 Session Local SQL DB Copyright © 2010 - Kaazing Corporation. All rights reserved.

Cookies vs. Web Storage • Cookies are limited in size • Cookies are transferred back and forth on every request (bandwidth) • Cookies are visible on the network (security) • Data leaks (while switching tabs) • Web Storage provides a simple API for storing values in easily retrievable JavaScript objects which persist across page loads 117 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Browser Support for Web SQL Database • Chrome 3.0+ • Safari 3.2+ • Opera 10.5+ • Note: Web SQL Database is based on SQLite and listed as stalled in the WHATWG spec. Indexed Database (a.k.a WebSimpleDB) is simpler and with no specific SQL database version, but not implemented yet. 120 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Offline Web Applications • Offline Web Applications o HTML5 allows detection of online/offline mode o Users can continue to interact with web applications and documents when their network connection is unavailable o Example: Gmail (Moving away from Gears) • Use a cache manifest file with details about files to be cached • Browsers cache data is in the application cache 124 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Other HTML5 Features • Drag and Drop Mechanism, o Currently only in Firefox 3.5+ • History o Includes nested browsing contexts o Not widely supported yet • ContentEditable o Editable elements o HTML5 provides a formalization of what is already implemented in HTML4 (all browsers) 126 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 IDEs and Tools • Currently limited HTML5 IDE support o SEEdit (Text editor) • HTML5 simplicity reduces work • Advanced browser development tools allow for “semi-rapid” development and live coding o Safari Web Inspector o Chrome Developer console o Firefox Firebug Add-on and Opera Firefly • more IDE support as specification solidifies • In the meantime, browser detection and feature emulation is growing 129 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Helper Tools • modernizr o Small, simple JavaScript library that checks support for HTML5 and CSS3 features o Moves away from user-agent sniffing and uses feature detection instead o http://www.modernizr.com/ • html5shiv o Creates the new HTML5 DOM elements in Internet Explorer so that styles can be applied to them o http://code.google.com/p/html5shiv/ 130 Copyright © 2010 - Kaazing Corporation. All rights reserved.

HTML5 Feature Emulation • Google Gears • Flash plugins • JavaScript-based emulations • Exporercanvas—Canvas emulation for Internet Explorer: http://code.google.com/p/explorercanvas/ • SVG Web Toolkit—SVG in Internet Explorer: http://code.google.com/p/svgweb/ • WebSocket emulation for HTML4 browsers: Kaazing WebSocket Gateway 131 www.kaazing.com Copyright © 2010 - Kaazing Corporation. All rights reserved.

Moving Away From Flash • Reasons: iPad does not support Flash • Flash content can in some cases be converted • Various HTML5 Canvas converters: o Flash CS5 Export to Canvas: http://www.9to5mac.com/Flash-html5-canvas- 35409730 o Opacity: http://likethought.com/opacity/ o Illustrator to Canvas: http://webdev.stephband.info/canvas/convert.html 132 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Testing and Deploying • Testing HTML5 Applications is not much different from HTML4 testing • Check for feature support in target browsers • Recent browsers provide better debugging capabilities (extensive debug consoles) o Firebug o Webkit-based inspector o Dragonfly • Additional QA tools o Dynatrace (performance) 133 o Wireshark (wire traffic inspection) Copyright © 2010 - Kaazing Corporation. All rights reserved.

Mobile HTML5 Applications • HTML5 applications served in a browser, therefore essentially not any different • Feature support may be different for mobile devices (for example, Geolocation on Safari Desktop vs. iPhone) • Widgets and iAd developments 134 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Microsoft IE and HTML5 • IE8 implementations for some parts of HTML5 • Recently joined HTML5 graphics working group (12/09) • “Doubling down” in IE9 (9th time’s a charm) o Audio o Video o SVG o CSS3 o 2D Acceleration o Does not run on XP 136 Copyright © 2010 - Kaazing Corporation. All rights reserved.

What’s Next? • Candidate Recommendation 2012 • Proposed Recommendation 2022 • There are already various features on the roadmap that will not make it into HTML5 o device element o ping attribute • Maybe just “HTML” (not version 6)? 137 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Resources • “When Can I Use?” a website with up-to-date HTML5 Feature support matrix: http://a.deveria.com/caniuse • WHATWG HTML5 Spec o http://www.whatwg.org/specs/web-apps/current-work/ • W3C HTML5 Spec o http://dev.w3.org/html5/spec/Overview.html 139 Copyright © 2010 - Kaazing Corporation. All rights reserved.

Copyright © 2010 Kaazing Corporation, All rights reserved. All materials, including labs and other handouts are property of Kaazing Corporation. Except when expressly permitted by Kaazing Corporation, you may not copy, reproduce, publish, or display any part of this training material, in any form, or by any means. 142 Copyright © 2010 - Kaazing Corporation. All rights reserved.

http://www.slideshare.net	983
http://infoblog.li	381
http://elearnppip.usm.my	217
http://hu.lesliesikos.com	173
http://www.learnnpublish.com	170
http://stefanopedone.wordpress.com	119
https://lms.kku.edu.sa	99
http://www.techgig.com	60
http://www.lesliesikos.com	49
http://thetechnicalweb.blogspot.in	41
http://localhost	36
http://websites.networksolutions.com	25
http://www.evolvebeyondmoney.com	20
http://evolvebeyondmoney.com	16
http://cms.lyon.novius.fr	11
http://vigo.navigo.fi	7
https://wiki.bouvet.no	6
http://www.brijj.com	6
https://blackboard.pace.edu	5
http://thetechnicalweb.blogspot.com	5
http://www.mashme.tv	4
http://thetechnicalweb.blogspot.de	4
http://facebook.slideshare.com	4
http://s.deeeki.com	4
http://webcache.googleusercontent.com	3
http://hypermedia2010.wordpress.com	3
http://192.168.4.115	2
http://translate.googleusercontent.com	2
http://www.ilearnipublish.com	2
http://development.cidde.pitt.edu	2
http://static.slidesharecdn.com	2
http://webfolio101.blogspot.com	2
http://sjaswinder.blogspot.com	2
http://142.mashmetv.appspot.com	1
http://www.yutzu.com	1
http://ecampustraining.dcccd.edu	1
http://mytutor.tut.ac.za	1
http://sjaswinder.blogspot.hk	1
http://webfolio101.blogspot.hk	1
http://cliqset.com	1
http://buenamusica.zoomblog.com	1
http://66.196.80.202	1
http://davidm.lyon.novius.fr	1
https://774022429-wave-opensocial.googleusercontent.com	1
http://paper.li	1
http://www.thetechnicalweb.blogspot.in	1

HTML5--The 30,000' View (A fast-paced overview of HTML5)

by Peter Lubbers

Accessibility

Categories

Upload Details

Usage Rights

46 Embeds 2,478

Statistics

HTML5--The 30,000’ View (A fast-paced overview of HTML5) Presentation Transcript