Real solutions, no tricks
Upcoming SlideShare
Loading in...5

Real solutions, no tricks



English version of a talk given at SAE Alumni Convention 2011 in Berlin, covering modern web development with HTML5 and CSS3

English version of a talk given at SAE Alumni Convention 2011 in Berlin, covering modern web development with HTML5 and CSS3



Total Views
Views on SlideShare
Embed Views



3 Embeds 444 442 1 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-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

Real solutions, no tricks Real solutions, no tricks Presentation Transcript

  • Real solutions, no tricks!
  • 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
  • Less documents,more applications
  • Missing controls
  • What can we do with CSS 2?
  • ‣ text formats‣ colours for fore- and background‣ positioning‣ floats‣ images are needed for many solutions‣ sometimes extra markup is needed for image- based solutions‣ transparence with side effects
  • HTML5-Highlights
  • One Doctype to rule them all<!DOCTYPE html>
  • Links around block elements
  • New semantic elements
  • New HTML5-Elements
  • New semantic elements‣ On many occasions a replacement for DIV.‣ Based on the actual practise on the web.‣ No special functions in the browser. Just new elements.‣ WAI-ARIA inclusive!
  • New semantic‣ fine structure of the content‣ Browser takes on the headline hierarchy. On complex pages this is great! Outline-algorithm
  • The outline-algorithm
  • Headlines‣ HTML4/XHTML: 6 headlines‣ HTML5: endless headlines
  • ‣ 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 defined.‣ These elemens are defining explicitely a section: ‣ <body>, <section>, <article>, <aside>, <footer>, <header>, <nav>
  • Each section has its own headings-hierarchy
  • the outline - uncertainty from an MDN-article Online-Outliner-Tool
  • Does this threaten us?
  • Think of the consequences!
  • ‣ HTML5-pages work in old browsers only via javascript. This concerns mainly IE including version 8.
  • With Javascript
  • Without Javascript
  • HTML5-formelements
  • HTML5-formelements
  • Appropriatescreen keyboard
  • Date Chrome 15 dev Firefox 5Opera 11.5
  • The placeholder-attribute
  • 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 ( ‣ Use polyfills ‣ wiki/HTML5-Cross-Browser-Polyfills
  • Which gap is filled by CSS3?
  • new layout-modelmore possibilities with borders and backgrounds Less images animations new selectors
  • transparency with rgba() rounded corners gradientstransitions media-queries calc() multiple columns
  • The pros‣ Less decorative images are needed‣ Less Javascript is needed.‣ Animations and transitions via CSS are faster than via Javascript.‣ The sourcecode will be leaner and better readable as HTML is rarely used for decorative purpose.
  • The consThere are none!
  • Okay, a small one!
  • modern selectors
  • ‣ Old IE (including version 8) don‘t understand them!‣ Those browser can be helped via Javascript.‣ If those selections aren‘t „vital“ the use of Javascript is okay.
  • Can I useCSS3 and HTML5 today?
  • yes and no
  • Some new properties aren‘timplemented in any browser.
  • Does this work in IE, too?
  • Progress depends on theslowest because of its wide distribution.
  • Old IE-versions ...
  • The Web is inherently flexible
  • „Responsive Design“is no new invention, despite the hype!
  • The consumer can useinformation from the Internet as he likes.
  • important insight:There can not be THE ONE form of representation!
  • Our Layout is only a recommendation!
  • Agree early on thedevelopment strategy
  • IE ≠ modern
  • Progressive Enhancement ‣ Focus is on the content
  • Graceful Degredation ‣ Focus is on the most modern browsers ‣ old browsers get a downgraded version
  • Brutal Degredation including IE8 modern browsers
  • How to deal with IE
  • Fallback
  • ‣ Microsoft participates at the technical improvement of the internet starting with IE9.‣ For most techniques it doesn‘t matter if we talk about IE6 or IE8.‣ Some may be simulated by Javascript.‣ Some may be simulated by IE-filters.‣ Apart from that: graceful degredation / progressive enhancement
  • Even with moderntechniques you can do nonsense!
  • CSS3 ≠ always useful
  • Frameworks/Tools
  • The three most important best practices Think Investigate Experiment
  • Twitter: @FlockeSlideshare: Flocke669
  • Jens Grochtdreis Präsentation steht unterder Creative Commons Lizenz„Attribution-ShareAlike 2.0“