3. Why html5?
•“We're betting big on HTML 5.”
• - Vic Gundotra, Google
•“The world is moving to HTML5.
• - Steve Jobs, Apple
•“The future of the web is HTML5.”
• - Dean Hachamovitch, Microsoft
7. What is usable now?
Web workers
DOCTYPE
File API
Web SQL DB Form Controls
Web Sockets
Canvas
Web Messaging Geolocation
Refined/Restored
Elements Semantic Elements
Web Storage
8. What is usable now?
DOCTYPE
Form Controls
Canvas
Geolocation
Refined/Restored
Elements Semantic Elements
9. What is usable now?
DOCTYPE
Form Controls
Geolocation
Semantic Elements
10. What is usable now?
DOCTYPE
Form Controls
Semantic Elements
Geolocation
36. Polyfills...
“A polyfill, or polyfiller, is a piece of code (or plugin) that provides the technology that you, the developer,
expect the browser to provide natively. Flattening the API landscape if you will.”
- Remy Sharp (Founder Full Frontal JavaScript Conference)
“A shim that mimics a future API providing fallback functionality to older browsers.”
- Paul Irish (creator of Modernizr)
Examples @ https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills
40. Another technique...
“Bulletproof HTML5 technique:
Use a nested div with semantic class name”
- Tantek Celik (Mozilla)
<section><div class=”section”>
...
</div></section>
.section {/* styling */}
HTML4 successor webapps 1 + xhtml2 merged \n\n2009 W3C dropped XHTML2 to focus on HTML5\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
W3C did research on most commonly used class names, to come up with new semantic elements.\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
W3C did research on most commonly used class names, to come up with new semantic elements.\nBrowsers that dont recognise the elements ignore them ,meaning they cant be styled\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
polyfill is a piece of code added to the page to augment the browser with the tech you would expect it to provide natively.\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
polyfill is a piece of code added to the page to augment the browser with the tech you would expect it to provide natively.\n\nBrowsers that encounter tags that they dont recognise, will be ignored. Means they element can&#x2019;t be styled... however... Polyfills\n
\n
css fits in with the OOCSS technique whereby you never style elements only classnames, makes styling more reusable... should be doing this anyway!\n\nSome elements dont allow the div to be nested inside, so the div would wrap those elements instead ie hgroup\n
css fits in with the OOCSS technique whereby you never style elements only classnames, makes styling more reusable... should be doing this anyway!\n\nSome elements dont allow the div to be nested inside, so the div would wrap those elements instead ie hgroup\n
\n
\n
needs to have well designed fallback, not just for browser support, but also because users may choose not too share there location info, or no location info available.\n