HTML5 and CSS 3

brucel@opera.com, http://dev.opera.com www.brucelawson.co.uk twitter.com/brucel

HTML5: how did we get here? Bruce Lawson, Opera Software

2004 W3C focus on XHTML 2.0 and beyond... 11/01/10 http://www.flickr.com/photos/craiga/17071467/

XHTML 2: This is not my beautiful wife! <img /> 11/01/10

11/01/10

Paper to W3C, 2004 We consider Web Applications to be an important area that has not been adequately served by existing technologies… There is a rising threat of single-vendor solutions addressing this problem before jointly- developed specifications. http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html 11/01/10

Paper to W3C, 2004 ● 1. Backwards compatibility, and a clear migration path. ● 2. Well-defined error handling. ● 3. Users should not be exposed to authoring errors. ● 4. Practical use: every feature that goes into the Web- applications specifications must be justified by a practical use case. The reverse is not necessarily true. ● 5. Scripting is here to stay (but should be avoided where more convenient declarative mark-up can be used). ● 6. Avoid device-specific profiling. ● 7. Make the process open. 11/01/10

11/01/10

Design Principles - Compatibility • Support Existing Content • Do not Reinvent the Wheel • Pave the Cowpaths • Evolution Not Revolution www.w3.org/TR/html-design-principles/ 11/01/10

Design Principles - Utility • Solve Real Problems • Secure By Design • Separation of Concerns • DOM Consistency 11/01/10

Design Principles - Priority of Constituencies Consider users over authors over implementors over specifiers over theoretical purity. 11/01/10

HTML5: how did we get here? Bruce Lawson, Opera Software Staffordshire University / Stafford / 28 October 2010

Design Principles - Interoperability • Well-defined Behavior • Avoid Needless Complexity • Handle Errors 11/01/10

Design Principles - Universal Access • Media Independence • Support World Languages • Accessibility 11/01/10

HTML5 <!DOCTYPE html> 11/01/10

Geo SVG 11/01/10

SVG 11/01/10

CSS 11/01/10

11/01/10

New Exciting Web Technology 11/01/10

HTML5 does not replace HTML 4.01 11/01/10

HTML5 has more bling! 11/01/10

HTML5 is umbrella term: markup elements and JavaScript APIs 11/01/10

11/01/10

Top 20 class names 1. footer 11. button 2. menu 12. main 3. style1 13. style3 4. msonormal 14. small 5. text 15. nav 6. content 16. clear 7. title 17. search 8. style2 18. style4 9. header 19. logo 10. copyright 20. body 11/01/10 http://devfiles.myopera.com/articles/572/classlist-url.htm

Top 20 id names 1. footer 11. search 2. content 12. nav 3. header 13. wrapper 4. logo 14. top 5. container 15. table2 6. main 16. layer2 7. table1 17. sidebar 8. menu 18. image1 9. layer1 19. banner 10. autonumber1 20. navigation 11/01/10 http://devfiles.myopera.com/articles/572/idlist-url.htm

Where does that highway go to? ● Build an HTML5 page ● See that HTML5 is real world – document what browsers do now and extend that ● Use some new structural elements and style them with CSS ● Chuck in an intelligent form

HTML5 and CSS 3

by brucelawson on Nov 01, 2010

Accessibility

Categories

Upload Details

Usage Rights

1 Embed 76

Statistics

HTML5 and CSS 3 Presentation Transcript