<?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>HTML 5 &#187; Events</title>
	<atom:link href="http://www.htmlfive.net/category/events/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.htmlfive.net</link>
	<description>A central location for HTML5 news and updates</description>
	<lastBuildDate>Tue, 31 Aug 2010 10:55:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Supporting New Elements in IE</title>
		<link>http://www.htmlfive.net/supporting-new-elements-in-ie/</link>
		<comments>http://www.htmlfive.net/supporting-new-elements-in-ie/#comments</comments>
		<pubDate>Wed, 07 Jan 2009 16:26:28 +0000</pubDate>
		<dc:creator>Lachlan Hunt</dc:creator>
				<category><![CDATA[Browsers]]></category>
		<category><![CDATA[DOM]]></category>
		<category><![CDATA[Elements]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[Syntax]]></category>

		<guid isPermaLink="false">http://blog.whatwg.org/?p=484</guid>
		<description><![CDATA[<p>Internet Explorer poses a small challenge when it comes to making use of the new elements introduced in HTML5.  Among others, these include elements like <code>section</code>, <code>article</code>, <code>header</code> and <code>footer</code>. The problem is that due to the way parsing works in IE, these elements are not recognised properly and result in an anomalous DOM representation.</p>

<p>To illustrate, consider this simple document fragment:</p>

<pre>&#60;body&#62;
  &#60;section&#62;
    &#60;p&#62;This is an example&#60;/p&#62;
  &#60;/section&#62;
&#60;/body&#62;</pre>

<p>Strangely, IE 6, 7 and 8 all fail to parse the <code>section</code> element properly and the resulting DOM looks like this.</p>

<ul>
	<li><code>BODY</code>
		<ul>
			<li><code>SECTION</code></li>
			<li><code>P</code>
				<ul>
					<li><code>#text</code>: This is an example</li>
				</ul>
			</li>
			<li><code>/SECTION</code></li>
		</ul>
	</li>
</ul>

<p>Notice how IE actually creates 2 empty elements.  One named <code>SECTION</code> and the other named <code>/SECTION</code>. Yes, it really is parsing the end tag as a start tag for an unknown empty element.</p>

<p>There is a handy workaround available to address this problem, which was first revealed in <a href="http://intertwingly.net/blog/2008/01/22/Best-Standards-Support#c1201006277">a comment by Sjoerd Visscher</a>.

The basic concept is that by using <code>document.createElement(<var>tagName</var>)</code> to create each of the unknown elements, the parser in IE then recognises those elements and parses them in a more reasonable and useful way. e.g. By using the following script:</p>

<pre>document.createElement("section");</pre>

<p>The resulting DOM for the fragment given above looks like this:</p>

<ul>
	<li><code>BODY</code>
		<ul>
			<li><code>section</code>
				<ul>
					<li><code>P</code>
						<ul>
							<li><code>#text</code>: This is an example</li>
						</ul>
					</li>
				</ul>
			</li>
		</ul>
	</li>
</ul>

<p>This same technique works for all unknown elements in IE 6, 7 and 8.  Note that there is a known bug that prevented this from working in IE 8 beta 2, but this has since been resolved in the latest non-public technical preview.</p>

<p>For convenience, Remy Sharp has written and <a href="http://remysharp.com/2009/01/07/html5-enabling-script/">published a simple script</a> that provides this enhancement for all new elements in the current draft of HTML5, which you can download and use.</p>

<p>This script is not needed for other browsers. Opera 9, Firefox 3 and Safari 3 all parse unknown elements in a more reasonable way by default. Note, however, that Firefox 2 does suffer from some related problems, for which there is unfortunately no known solution; but it is hoped that given the faster upgrade cycle for users of Firefox, relatively speaking compared with IE, Firefox 2 won't pose too much of a problem in the future.</p>]]></description>
			<content:encoded><![CDATA[<p>Internet Explorer poses a small challenge when it comes to making use of the new elements introduced in HTML5.  Among others, these include elements like <code>section</code>, <code>article</code>, <code>header</code> and <code>footer</code>. The problem is that due to the way parsing works in IE, these elements are not recognised properly and result in an anomalous DOM representation.</p>

<p>To illustrate, consider this simple document fragment:</p>

<pre>&lt;body&gt;
  &lt;section&gt;
    &lt;p&gt;This is an example&lt;/p&gt;
  &lt;/section&gt;
&lt;/body&gt;</pre>

<p>Strangely, IE 6, 7 and 8 all fail to parse the <code>section</code> element properly and the resulting DOM looks like this.</p>

<ul>
	<li><code>BODY</code>
		<ul>
			<li><code>SECTION</code></li>
			<li><code>P</code>
				<ul>
					<li><code>#text</code>: This is an example</li>
				</ul>
			</li>
			<li><code>/SECTION</code></li>
		</ul>
	</li>
</ul>

<p>Notice how IE actually creates 2 empty elements.  One named <code>SECTION</code> and the other named <code>/SECTION</code>. Yes, it really is parsing the end tag as a start tag for an unknown empty element.</p>

<p>There is a handy workaround available to address this problem, which was first revealed in <a href="http://intertwingly.net/blog/2008/01/22/Best-Standards-Support#c1201006277">a comment by Sjoerd Visscher</a>.

The basic concept is that by using <code>document.createElement(<var>tagName</var>)</code> to create each of the unknown elements, the parser in IE then recognises those elements and parses them in a more reasonable and useful way. e.g. By using the following script:</p>

<pre>document.createElement("section");</pre>

<p>The resulting DOM for the fragment given above looks like this:</p>

<ul>
	<li><code>BODY</code>
		<ul>
			<li><code>section</code>
				<ul>
					<li><code>P</code>
						<ul>
							<li><code>#text</code>: This is an example</li>
						</ul>
					</li>
				</ul>
			</li>
		</ul>
	</li>
</ul>

<p>This same technique works for all unknown elements in IE 6, 7 and 8.  Note that there is a known bug that prevented this from working in IE 8 beta 2, but this has since been resolved in the latest non-public technical preview.</p>

<p>For convenience, Remy Sharp has written and <a href="http://remysharp.com/2009/01/07/html5-enabling-script/">published a simple script</a> that provides this enhancement for all new elements in the current draft of HTML5, which you can download and use.</p>

<p>This script is not needed for other browsers. Opera 9, Firefox 3 and Safari 3 all parse unknown elements in a more reasonable way by default. Note, however, that Firefox 2 does suffer from some related problems, for which there is unfortunately no known solution; but it is hoped that given the faster upgrade cycle for users of Firefox, relatively speaking compared with IE, Firefox 2 won't pose too much of a problem in the future.</p><p></p><p>This item was originally posted at: <a href='http://blog.whatwg.org'>http://blog.whatwg.org</a> and is licensed under the <a href='http://www.opensource.org/licenses/mit-license.php'>MIT license</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.htmlfive.net/supporting-new-elements-in-ie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Tech Talk: HTML5 demos</title>
		<link>http://www.htmlfive.net/google-tech-talk-html5-demos/</link>
		<comments>http://www.htmlfive.net/google-tech-talk-html5-demos/#comments</comments>
		<pubDate>Fri, 26 Sep 2008 23:49:13 +0000</pubDate>
		<dc:creator>Ian Hickson</dc:creator>
				<category><![CDATA[Browser API]]></category>
		<category><![CDATA[Browsers]]></category>
		<category><![CDATA[Conformance Checking]]></category>
		<category><![CDATA[DOM]]></category>
		<category><![CDATA[Elements]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[Forms]]></category>
		<category><![CDATA[Multimedia]]></category>
		<category><![CDATA[Syntax]]></category>
		<category><![CDATA[WHATWG]]></category>

		<guid isPermaLink="false">http://blog.whatwg.org/?p=300</guid>
		<description><![CDATA[<p>I gave a talk at Google on Monday demonstrating the various features of HTML5 that are implemented in browsers today. The video is now on YouTube, so now you too can watch and laugh at my lame presentation skills!</p>
<p></p>
<p>The segments of this talk are as follows. Some of the demos are available online for you to play with and are linked to from the following list:</p>
<ol>
 <li> Introduction
 </li><li> <a href="http://whatwg.org/demos/2008-sept/video/video.html"><code>&#60;video&#62;</code></a> (00:35)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/gadget-host/host.html"><code>postMessage()</code></a> (05:40)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/editor/editor.html"><code>localStorage</code></a> (15:20)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/wizard/step1.html"><code>sessionStorage</code></a> (21:00)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/dnd/dnd.html">Drag and Drop API</a> (29:05)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/hashchange/hashchange.html"><code>onhashchange</code></a> (37:30)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/widgets/">Form Controls</a> (40:50)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/color/color.html"><code>&#60;canvas&#62;</code></a> (56:55)
 </li><li> <a href="http://html5.validator.nu/">Validation</a> (1:07:20)
 </li><li> Questions and Answers (1:09:35)
</li></ol>
<p>If you're very interested in watching my typos, the high quality version of <a href="http://www.youtube.com/watch?v=xIxDJof7xxQ&#38;eurl=http://www.whatwg.org/demos/2008-sept/">the video on the YouTube site</a> is clear enough to see the text being typed. More details about the demos can be found on the corresponding <a href="http://whatwg.org/demos/2008-sept/">demo page</a>.</p>]]></description>
			<content:encoded><![CDATA[<p>I gave a talk at Google on Monday demonstrating the various features of HTML5 that are implemented in browsers today. The video is now on YouTube, so now you too can watch and laugh at my lame presentation skills!</p>
<p></p>
<p>The segments of this talk are as follows. Some of the demos are available online for you to play with and are linked to from the following list:</p>
<ol>
 <li> Introduction
 </li><li> <a href="http://whatwg.org/demos/2008-sept/video/video.html"><code>&lt;video&gt;</code></a> (00:35)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/gadget-host/host.html"><code>postMessage()</code></a> (05:40)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/editor/editor.html"><code>localStorage</code></a> (15:20)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/wizard/step1.html"><code>sessionStorage</code></a> (21:00)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/dnd/dnd.html">Drag and Drop API</a> (29:05)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/hashchange/hashchange.html"><code>onhashchange</code></a> (37:30)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/widgets/">Form Controls</a> (40:50)
 </li><li> <a href="http://whatwg.org/demos/2008-sept/color/color.html"><code>&lt;canvas&gt;</code></a> (56:55)
 </li><li> <a href="http://html5.validator.nu/">Validation</a> (1:07:20)
 </li><li> Questions and Answers (1:09:35)
</li></ol>
<p>If you're very interested in watching my typos, the high quality version of <a href="http://www.youtube.com/watch?v=xIxDJof7xxQ&#38;eurl=http://www.whatwg.org/demos/2008-sept/">the video on the YouTube site</a> is clear enough to see the text being typed. More details about the demos can be found on the corresponding <a href="http://whatwg.org/demos/2008-sept/">demo page</a>.</p><p></p><p>This item was originally posted at: <a href='http://blog.whatwg.org'>http://blog.whatwg.org</a> and is licensed under the <a href='http://www.opensource.org/licenses/mit-license.php'>MIT license</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.htmlfive.net/google-tech-talk-html5-demos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interview about HTML5 on Boagworld</title>
		<link>http://www.htmlfive.net/interview-about-html5-on-boagworld/</link>
		<comments>http://www.htmlfive.net/interview-about-html5-on-boagworld/#comments</comments>
		<pubDate>Wed, 02 Jul 2008 23:14:44 +0000</pubDate>
		<dc:creator>Lachlan Hunt</dc:creator>
				<category><![CDATA[Events]]></category>

		<guid isPermaLink="false">http://blog.whatwg.org/?p=196</guid>
		<description><![CDATA[<p>Boagworld is a web design and development podcast based in the UK.  In <a href="http://boagworld.com/podcast/124/">today's episode</a>, they interview me about HTML5.  In it, we discuss the current state of HTML5, some of the new features that are currently, or are being implemented, and what we can expect in the future.</p>]]></description>
			<content:encoded><![CDATA[<p>Boagworld is a web design and development podcast based in the UK.  In <a href="http://boagworld.com/podcast/124/">today's episode</a>, they interview me about HTML5.  In it, we discuss the current state of HTML5, some of the new features that are currently, or are being implemented, and what we can expect in the future.</p><p></p><p>This item was originally posted at: <a href='http://blog.whatwg.org'>http://blog.whatwg.org</a> and is licensed under the <a href='http://www.opensource.org/licenses/mit-license.php'>MIT license</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.htmlfive.net/interview-about-html5-on-boagworld/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
