<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Digital Marketing Blog by Soak Digital &#187; html5</title>
	<atom:link href="http://www.soak.co.uk/blog/tag/html5/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.soak.co.uk/blog</link>
	<description>a digital marketing agency</description>
	<lastBuildDate>Wed, 23 Nov 2011 15:51:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Learning HTML5: Getting started</title>
		<link>http://www.soak.co.uk/blog/learning-html5-getting-started/</link>
		<comments>http://www.soak.co.uk/blog/learning-html5-getting-started/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 09:21:12 +0000</pubDate>
		<dc:creator>ronan.sprake</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[html5]]></category>

		<guid isPermaLink="false">http://www.soak.co.uk/blog/?p=482</guid>
		<description><![CDATA[The HTML5 working group doesn&#8217;t do PR. This became evident last year in the negative blog posts after Ian Hickson (lead editor) set 2022 as the target date for a final proposed recommendation. Unfortunately, this was misenterpreted as the date HTML5 would be ready for use, which isn&#8217;t true at all. Web specifications have a [...]]]></description>
			<content:encoded><![CDATA[<p>The HTML5 working group doesn&#8217;t do PR. This became evident last year in the negative blog posts after Ian Hickson (lead editor) set 2022 as the target date for a final proposed recommendation. Unfortunately, this was misenterpreted as the date HTML5 would be ready for use, which isn&#8217;t true at all. Web specifications have a notoriously slow moving approval process, where drafts are proposed and discussed over many years. However, as CSS2.1 has shown, the technology can be used well before final approval is reached.<span id="more-482"></span></p>
<p>Since the HTML5 specification is subject to change and is lacking support in IE, I wouldn&#8217;t recommend getting too carried away with things, but it&#8217;s worth learning the basics and knowing the useful elements. The <a href="http://html5doctor.com/glossary/">HTML5 glossary</a> is a good place to start. </p>
<h2>&lt;!doctype html&gt;</h2>
<p>You need to use the HTML5 shiv technique (outlined in <a href="http://www.soak.co.uk/blog/2009/12/styling-html5-elements-in-ie/">this earlier post</a>) which consists of a Javascript snippet that enables HTML5 element styling in IE. The main thing to remember before you get started, is that there is currently no way to style nested HTML5 elements in IE &#8211; quite a major restriction &#8211; but this shouldn&#8217;t stop you from getting started with HTML5-inspired layouts.</p>
<p>Using the minimal HTML5 doctype (&lt;!doctype html&gt;) you can validate as-you-go with the <a href="http://validator.w3.org/">W3 validator</a>.</p>
<p>Talking of inspiration, that&#8217;s the next step &#8211; check out the sites already experimenting with HTML5, there are some nice <a href="http://anino.sining.net/">real-world examples</a> showcased in the <a href="http://html5gallery.com/">HTML5 gallery</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.soak.co.uk/blog/learning-html5-getting-started/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Styling HTML5 elements in IE</title>
		<link>http://www.soak.co.uk/blog/styling-html5-elements-in-ie/</link>
		<comments>http://www.soak.co.uk/blog/styling-html5-elements-in-ie/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 14:14:44 +0000</pubDate>
		<dc:creator>ronan.sprake</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[internet explorer]]></category>
		<category><![CDATA[javascript]]></category>

		<guid isPermaLink="false">http://www.soak.co.uk/blog/?p=446</guid>
		<description><![CDATA[A quick tip on how to enable HTML5 elements such as &#60;section&#62; and &#60;header&#62; in Internet Explorer. I&#8217;m afraid it does require Javascript: document.createElement("section") This workaround for all unrecognised HTML5 elements is available in the form of a tiny 352 bite JS file, from Google Code (uploaded here for your convenience!) If only it were [...]]]></description>
			<content:encoded><![CDATA[<p>A quick tip on how to enable HTML5 elements such as &lt;section&gt; and &lt;header&gt; in Internet Explorer. I&#8217;m afraid it does require Javascript:</p>
<p><code>document.createElement("section")</code><span id="more-446"></span></p>
<p>This workaround for all unrecognised HTML5 elements is available in the form of a tiny 352 bite JS file, from <a href="http://code.google.com/p/html5shiv/">Google Code</a> (uploaded <a href='http://www.soak.co.uk/blog/wp-content/uploads/2009/12/html5.js'>here</a> for your convenience!)</p>
<h2>If only it were that easy!</h2>
<p>There is one major caveat to this tip, in that I haven&#8217;t yet found a way to nest HTML5 elements reliably. This means that there is currently no way to make IE understand this markup:</p>
<p><code>&lt;section&gt;&lt;header&gt;&lt;/header&gt;&lt;/section&gt;</code></p>
<p>As usual, where Internet Explorer is concerned, things are even more convoluted. IE recognises the new elements as XML rather than HTML. This shouldn&#8217;t be a major problem, but knowing this helps to avoid potential .nodeName headaches!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.soak.co.uk/blog/styling-html5-elements-in-ie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

