<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Why browsers treat HTML5 elements as inline</title>
	<atom:link href="http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 14:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Scott Plumlee</title>
		<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/comment-page-1/#comment-678243</link>
		<dc:creator>Scott Plumlee</dc:creator>
		<pubDate>Mon, 12 Jul 2010 11:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=2241#comment-678243</guid>
		<description>Thanks for the response Bruce. That&#039;s the link I needed to understand how they set what was allowed in what. I&#039;m going to have to read about content models in HTML5 and I&#039;ll be back with more questions, I&#039;m sure. You and the other doctors are a great resource.</description>
		<content:encoded><![CDATA[<p>Thanks for the response Bruce. That&#8217;s the link I needed to understand how they set what was allowed in what. I&#8217;m going to have to read about content models in HTML5 and I&#8217;ll be back with more questions, I&#8217;m sure. You and the other doctors are a great resource.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/comment-page-1/#comment-678242</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Mon, 12 Jul 2010 11:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=2241#comment-678242</guid>
		<description>Hi Scott

HTML4 defined some elements as block and some as inline, so the validators used those defintions http://www.w3.org/TR/html401/struct/global.html#h-7.5.3

HTML5 doesn&#039;t use that terminology as that implies some form of presentation and, of course, presentation and semantics are different beasts.</description>
		<content:encoded><![CDATA[<p>Hi Scott</p>
<p>HTML4 defined some elements as block and some as inline, so the validators used those defintions <a href="http://www.w3.org/TR/html401/struct/global.html#h-7.5.3" rel="nofollow">http://www.w3.org/TR/html401/struct/global.html#h-7.5.3</a></p>
<p>HTML5 doesn&#8217;t use that terminology as that implies some form of presentation and, of course, presentation and semantics are different beasts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Plumlee</title>
		<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/comment-page-1/#comment-678239</link>
		<dc:creator>Scott Plumlee</dc:creator>
		<pubDate>Mon, 12 Jul 2010 10:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=2241#comment-678239</guid>
		<description>This brings up a question I&#039;ve wondered about for a while. If the display of an element is inline by default, how do validators decide that something is valid or not valid if the spec states that an element may only contain block or inline content? For instance, a &lt;dt&gt; element may only have inline content inside it (http://www.w3.org/TR/html401/struct/lists.html#h-10.3). It seems that the validation of an HMTL document is then dependent on the display property of the element, rather than something intrinsic to the element itself.  Do the validators contain their own internal stylesheet rules, or do they have some other set of rules that say these items are block, these are inline?</description>
		<content:encoded><![CDATA[<p>This brings up a question I&#8217;ve wondered about for a while. If the display of an element is inline by default, how do validators decide that something is valid or not valid if the spec states that an element may only contain block or inline content? For instance, a &lt;dt&gt; element may only have inline content inside it (<a href="http://www.w3.org/TR/html401/struct/lists.html#h-10.3" rel="nofollow">http://www.w3.org/TR/html401/struct/lists.html#h-10.3</a>). It seems that the validation of an HMTL document is then dependent on the display property of the element, rather than something intrinsic to the element itself.  Do the validators contain their own internal stylesheet rules, or do they have some other set of rules that say these items are block, these are inline?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Yates</title>
		<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/comment-page-1/#comment-646698</link>
		<dc:creator>Andrew Yates</dc:creator>
		<pubDate>Tue, 24 Nov 2009 19:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=2241#comment-646698</guid>
		<description>Thank you Bruce for your HTML5 posts and articles in various places across the web. I have to say you are the biggest driving force in me changing my site and making it HTML5. 

Was nice to take the plunge and get it out there. Especially as I started it as &quot;messing around&quot; then deciding it was better than my old theme.

Keep up the good work.

Andy</description>
		<content:encoded><![CDATA[<p>Thank you Bruce for your HTML5 posts and articles in various places across the web. I have to say you are the biggest driving force in me changing my site and making it HTML5. </p>
<p>Was nice to take the plunge and get it out there. Especially as I started it as &#8220;messing around&#8221; then deciding it was better than my old theme.</p>
<p>Keep up the good work.</p>
<p>Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bruce</title>
		<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/comment-page-1/#comment-643210</link>
		<dc:creator>bruce</dc:creator>
		<pubDate>Wed, 18 Nov 2009 17:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=2241#comment-643210</guid>
		<description>You&#039;re right, of course, David for the more sophisticated elements. But using -say- &lt;code&gt;mark&lt;/code&gt; as an example, all the browser needs to know is how to style it.

A browser may decide to do something sexy with mark, of course - like add each mark to a list in a sidebar.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, of course, David for the more sophisticated elements. But using -say- <code>mark</code> as an example, all the browser needs to know is how to style it.</p>
<p>A browser may decide to do something sexy with mark, of course &#8211; like add each mark to a list in a sidebar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Mabbett</title>
		<link>http://www.brucelawson.co.uk/2009/why-browsers-treat-html5-elements-as-inline/comment-page-1/#comment-643137</link>
		<dc:creator>Andy Mabbett</dc:creator>
		<pubDate>Wed, 18 Nov 2009 15:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=2241#comment-643137</guid>
		<description>Mmmm, cheesecake…</description>
		<content:encoded><![CDATA[<p>Mmmm, cheesecake…</p>
]]></content:encoded>
	</item>
</channel>
</rss>

