As you may have noticed, we’ve not written one of these posts in a while. That’s not down to us not receiving them, though. Government cutbacks have hit health services hard, so decisions had to be made. Well, that and the fact that we’ve all just been manically busy with our day jobs.
The clinic is getting busy with more HTML5 ailments! This week, we’ll cover the separation of formatting and content, custom elements, using aside for social links, sections with no visible titles, and canvas in the DOM.
You’ve already learned about the
<canvas> elements, but did you know that they were designed to be used together? In fact, the two elements are absolutely wondrous when you combine them together. I’m going to show off a few super-simple demos using the two elements together, which should help suggest cool future projects for you fellow web authors.
The clinic is getting busy with more HTML5 ailments. This week, we’ll cover server-side validation, immutable images with
<canvas>, retrieving drawn objects from a
<canvas>, creating custom tags, the
role attribute, and the effects of
<hgroup> on SEO.
If the video element is the poster boy of HTML5, then canvas is definitely Danny Zuko. The canvas element is (still) part of the HTML5 specification, but the 2D drawing API has been moved into a separate document (in case you go looking and can’t find it).
The clinic is busy as ever with more HTML5 ailments. This week, we’ll show you how (and whether) to store a
<canvas> on the server, whether to use
<meter>, more on
placeholder attribute, and HTML5 minification.
The clinic is getting busy with more HTML5 ailments. This week, we’ll cover using sections within a footer,
<canvas> vs. Flash security, why HTML5 elements are treated as inline, using offline with storage, and marking up block quotes.
After a while on the fringes of our collective consciousness, HTML5 is finally getting the attention it deserves. The development community (as typified by the SuperFriends) has come together to debate practical elements of the spec, argue over the inclusion of controversial elements, and assess the timeframe over which we can unleash HTML5 in the wild.