Jens Grochtdreis‣ Frontend developer‣ 10 years work in agencies‣ 12 years work in and for the web‣ Founder of the Webkrauts‣ Blogger‣ Author for several developer-magazines‣ technical book-editor for Galileo, OReilly, Pearson
‣ text formats‣ colours for fore- and background‣ positioning‣ ﬂoats‣ images are needed for many solutions‣ sometimes extra markup is needed for image- based solutions‣ transparence with side effects
‣ Each content inside the <body>-element is part of a "section". Sections can be nested.‣ The <body>-element is the main section. Further sections are implicitely (h1 - h6) or explicitly deﬁned.‣ These elemens are deﬁning explicitely a section: ‣ <body>, <section>, <article>, <aside>, <footer>, <header>, <nav>
Each section has its own headings-hierarchyhttps://developer.mozilla.org/en/Sections_and_Outlines_of_an_HTML5_document
the outline - uncertainty from an MDN-article Online-Outliner-Toolhttp://gsnedders.html5.org/outliner/process.py
Does this threaten us?https://github.com/cboone/hypsometric-css/blob/master/html5/html5-defaults.css#L426
What if a browser doesn‘tknow the new elements?
Then all new input-elements are rendered as <input type=“text“> and attributes get ignored.
Built-in Validation Opera 11.5 Mac Firefox 5 Mac Chrome 15 dev MacChrome doesn‘t play well with scaled pages and validation.
What if a browser doesn‘t know the validation? ‣ Ignore it! ( = Progressive enhancement) ‣ Load JS-alternatives with Modernizr (http://modernizr.com) ‣ Use polyﬁlls ‣ https://github.com/Modernizr/Modernizr/ wiki/HTML5-Cross-Browser-Polyﬁlls
Even with moderntechniques you can do nonsense!