<?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"
	>
<channel>
	<title>Comments on: Inline CSS should not be allowed in strict doctypes</title>
	<atom:link href="http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/feed/" rel="self" type="application/rss+xml" />
	<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/</link>
	<description>You have found Friendly Bit, a web development blog. I focus on client side technologies like CSS, HTML and Javascript. You find my articles below and categories to the right.</description>
	<pubDate>Sun, 12 Oct 2008 00:36:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: prezenty</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-30662</link>
		<dc:creator>prezenty</dc:creator>
		<pubDate>Wed, 28 May 2008 16:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-30662</guid>
		<description>This is interesting article, I did not it think that it yes. Interesting it knew persons about this how much. Sorry if I wrote bad there now my English is novice and I do not it write yet good.</description>
		<content:encoded><![CDATA[<p>This is interesting article, I did not it think that it yes. Interesting it knew persons about this how much. Sorry if I wrote bad there now my English is novice and I do not it write yet good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mogens overbeck</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-24418</link>
		<dc:creator>mogens overbeck</dc:creator>
		<pubDate>Sat, 19 May 2007 14:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-24418</guid>
		<description>In my view inline styles *are* actually a good thing, since you can use them during the initial markup phase - that's often the way I do it, anyway. I mark up, styling as I go, and in the end transfer the css to an external stylesheet, so for me it's just a handy way of speeding up the workflow. I see your point though, if it wasn't allowed, people would be forced to learn better development practices, but I'm not sure I agree that's the way to go about it :o)</description>
		<content:encoded><![CDATA[<p>In my view inline styles *are* actually a good thing, since you can use them during the initial markup phase - that&#8217;s often the way I do it, anyway. I mark up, styling as I go, and in the end transfer the css to an external stylesheet, so for me it&#8217;s just a handy way of speeding up the workflow. I see your point though, if it wasn&#8217;t allowed, people would be forced to learn better development practices, but I&#8217;m not sure I agree that&#8217;s the way to go about it :o)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Transparent PNGs and IE6 standalone - Friendly Bit</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-23797</link>
		<dc:creator>Transparent PNGs and IE6 standalone - Friendly Bit</dc:creator>
		<pubDate>Sat, 28 Apr 2007 19:44:39 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-23797</guid>
		<description>[...] Two background images later, one that the author could specify (added with a style tag in the head, not with inline styles), and one with the transparency. Everything worked flawlessly in Firefox, Opera, and IE7, as [...]</description>
		<content:encoded><![CDATA[<p>[...] Two background images later, one that the author could specify (added with a style tag in the head, not with inline styles), and one with the transparency. Everything worked flawlessly in Firefox, Opera, and IE7, as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Fraser</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-13682</link>
		<dc:creator>Sean Fraser</dc:creator>
		<pubDate>Sat, 13 Jan 2007 01:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-13682</guid>
		<description>Emil: I agree: inline styles should not be allowed in Strict documents. I found twisted irony in &lt;strong&gt;my&lt;/strong&gt; having to do so.</description>
		<content:encoded><![CDATA[<p>Emil: I agree: inline styles should not be allowed in Strict documents. I found twisted irony in <strong>my</strong> having to do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-13490</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Fri, 12 Jan 2007 05:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-13490</guid>
		<description>@Sean Fraser: I've done that too, real world projects sometimes require you to work with only inline styles. Thing is, the html of those sites are so bad it's just silly calling them valid anything. You're in there really mixing style and content in worse ways than we did in 1996! 

I've done the same, but I don't think that's an argument against removing it.</description>
		<content:encoded><![CDATA[<p>@Sean Fraser: I&#8217;ve done that too, real world projects sometimes require you to work with only inline styles. Thing is, the html of those sites are so bad it&#8217;s just silly calling them valid anything. You&#8217;re in there really mixing style and content in worse ways than we did in 1996! </p>
<p>I&#8217;ve done the same, but I don&#8217;t think that&#8217;s an argument against removing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Fraser</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-13454</link>
		<dc:creator>Sean Fraser</dc:creator>
		<pubDate>Fri, 12 Jan 2007 01:45:58 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-13454</guid>
		<description>When I read this in May I nodded and thought how true. Inline styles in Strict should not be done. However. I've recently had the &lt;em&gt;pleasure&lt;/em&gt; of working on a Strict site where I was not allowed to touch the style sheets but given access to the products' HTML content. [Styles sheets were in the CMS of the design agency; product pages were client accessible. Don't ask.] I used inline styles for new HTML elements. A real world website, indeed.</description>
		<content:encoded><![CDATA[<p>When I read this in May I nodded and thought how true. Inline styles in Strict should not be done. However. I&#8217;ve recently had the <em>pleasure</em> of working on a Strict site where I was not allowed to touch the style sheets but given access to the products&#8217; HTML content. [Styles sheets were in the CMS of the design agency; product pages were client accessible. Don't ask.] I used inline styles for new HTML elements. A real world website, indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-10231</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Sat, 23 Dec 2006 14:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-10231</guid>
		<description>@Jeremy Nicoll: The relation is clear, whether you choose to see it or not. Doctypes define what elements and attributes are allowed in a document. It could therefore disallow  the style attribute...

Why you shouldn't be allowed to use it "only once"? Because once rarely stay once when you deal with real world websites. If you've allowed one step away from the content/style separation you'll easily do more of them.</description>
		<content:encoded><![CDATA[<p>@Jeremy Nicoll: The relation is clear, whether you choose to see it or not. Doctypes define what elements and attributes are allowed in a document. It could therefore disallow  the style attribute&#8230;</p>
<p>Why you shouldn&#8217;t be allowed to use it &#8220;only once&#8221;? Because once rarely stay once when you deal with real world websites. If you&#8217;ve allowed one step away from the content/style separation you&#8217;ll easily do more of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Nicoll</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-10146</link>
		<dc:creator>Jeremy Nicoll</dc:creator>
		<pubDate>Sat, 23 Dec 2006 02:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-10146</guid>
		<description>The strict doctype has no relation to whether inline styles are used or not.  The main idea of CSS is to separate content and styling, and so inline styling is discouraged - but this is something that CSS experts generally encourage and has nothing to do with doctypes. In strict mode, inline styling is perfectly valid as style is a valid property of most objects.  The only time that I ever use inline styling is when I am applying a style to an element that I am only going to use once.  Why clutter up my CSS file with something that is only going to be used once?</description>
		<content:encoded><![CDATA[<p>The strict doctype has no relation to whether inline styles are used or not.  The main idea of CSS is to separate content and styling, and so inline styling is discouraged - but this is something that CSS experts generally encourage and has nothing to do with doctypes. In strict mode, inline styling is perfectly valid as style is a valid property of most objects.  The only time that I ever use inline styling is when I am applying a style to an element that I am only going to use once.  Why clutter up my CSS file with something that is only going to be used once?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pozycjonowanie</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-5843</link>
		<dc:creator>Pozycjonowanie</dc:creator>
		<pubDate>Fri, 20 Oct 2006 16:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-5843</guid>
		<description>Max, you shouldn’t add style attributes with JavaScript, you’re then mixing style and behaviour. Instead, you should add classes/ids and reference them in the stylesheet. Not ideal in a few cases, but the majority of the time that’s the best solution.</description>
		<content:encoded><![CDATA[<p>Max, you shouldn’t add style attributes with JavaScript, you’re then mixing style and behaviour. Instead, you should add classes/ids and reference them in the stylesheet. Not ideal in a few cases, but the majority of the time that’s the best solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Esqueça o atributo style. Estilos inline em doctype strict são resquícios do câncer de um passado sem padrões. &#187; Revolução Etc - Web Standards em uma casca de noz!</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-4068</link>
		<dc:creator>Esqueça o atributo style. Estilos inline em doctype strict são resquícios do câncer de um passado sem padrões. &#187; Revolução Etc - Web Standards em uma casca de noz!</dc:creator>
		<pubDate>Mon, 28 Aug 2006 16:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-4068</guid>
		<description>[...] Seguindo o exemplo de Emil Stenström qual a diferença entre os dois exemplos abaixo na sua opinião? [...]</description>
		<content:encoded><![CDATA[<p>[...] Seguindo o exemplo de Emil Stenström qual a diferença entre os dois exemplos abaixo na sua opinião? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: About Web Designing &#187; Blog Archive &#187; Inline CSS should not be allowed in strict doctypes</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2856</link>
		<dc:creator>About Web Designing &#187; Blog Archive &#187; Inline CSS should not be allowed in strict doctypes</dc:creator>
		<pubDate>Fri, 07 Jul 2006 06:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2856</guid>
		<description>[...] Instead, according to friendly bit, the strict doctype requires us to define all CSS in a different file. [...]</description>
		<content:encoded><![CDATA[<p>[...] Instead, according to friendly bit, the strict doctype requires us to define all CSS in a different file. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Perkins</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2147</link>
		<dc:creator>Justin Perkins</dc:creator>
		<pubDate>Fri, 23 Jun 2006 13:47:38 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2147</guid>
		<description>I'm with you on that one Emil, great discussion you promoted here :)</description>
		<content:encoded><![CDATA[<p>I&#8217;m with you on that one Emil, great discussion you promoted here :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2129</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Fri, 23 Jun 2006 08:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2129</guid>
		<description>@Justin Perkins: Of course I see your point too. Using inline styles is easier and &lt;em&gt;there are&lt;/em&gt; places where it makes sense. 

I would implement a tagcloud by picking 10 font-sizes (users won't notice the difference of 100 different levels) and make a class for each one of them. Then set the size for each tag to one of the above.

Let's just agree to disagree on that one.</description>
		<content:encoded><![CDATA[<p>@Justin Perkins: Of course I see your point too. Using inline styles is easier and <em>there are</em> places where it makes sense. </p>
<p>I would implement a tagcloud by picking 10 font-sizes (users won&#8217;t notice the difference of 100 different levels) and make a class for each one of them. Then set the size for each tag to one of the above.</p>
<p>Let&#8217;s just agree to disagree on that one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Perkins</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2123</link>
		<dc:creator>Justin Perkins</dc:creator>
		<pubDate>Fri, 23 Jun 2006 05:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2123</guid>
		<description>Sorry, that really sucked.

I posted what I was trying to say on my site if you want to see what I so poorly tried to explain.</description>
		<content:encoded><![CDATA[<p>Sorry, that really sucked.</p>
<p>I posted what I was trying to say on my site if you want to see what I so poorly tried to explain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Perkins</title>
		<link>http://friendlybit.com/css/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2121</link>
		<dc:creator>Justin Perkins</dc:creator>
		<pubDate>Fri, 23 Jun 2006 05:23:57 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/html/inline-css-should-not-be-allowed-in-strict-doctypes/#comment-2121</guid>
		<description>&#62; Just to get that out of the way, you shouldn’t open new windows. If the user is skilled enough to want it, he will know how to open them.

Ok, but I'm just trying to equate the anti-new window argument to the anti-inline style one. I think they are very similar, philosophically speaking.

So, we're talking tag clounds (ala Flickr vs. Technorati). If I want to implement a tag cloud like Flickr does (imo is the *proper* way to do it), what's the cost of doing it the dynamic CSS class way vs. inline styles. Is it worth it (not just to you, but to whoever you are billing/working for)?

&#62; That’s dynamic CSS right there which means it’s as much work writing it to a CSS class as writing it inline

I'm not buying that argument. Every one of your views (a purist like you has to be MVC right?) is passing up dynamic CSS to be stuffed into the document head? Talk about muddling up the code!

I don't see how this:
&lt;code&gt;&lt;em&gt;I love inline styles&lt;/em&gt;&lt;/code&gt;

Is worse than this:
&lt;code&gt;
&lt;em&gt;I hate inline styles&lt;/em&gt;&lt;/code&gt;

In fact, that is just too ludicrous to even insinuate.</description>
		<content:encoded><![CDATA[<p>&gt; Just to get that out of the way, you shouldn’t open new windows. If the user is skilled enough to want it, he will know how to open them.</p>
<p>Ok, but I&#8217;m just trying to equate the anti-new window argument to the anti-inline style one. I think they are very similar, philosophically speaking.</p>
<p>So, we&#8217;re talking tag clounds (ala Flickr vs. Technorati). If I want to implement a tag cloud like Flickr does (imo is the *proper* way to do it), what&#8217;s the cost of doing it the dynamic CSS class way vs. inline styles. Is it worth it (not just to you, but to whoever you are billing/working for)?</p>
<p>&gt; That’s dynamic CSS right there which means it’s as much work writing it to a CSS class as writing it inline</p>
<p>I&#8217;m not buying that argument. Every one of your views (a purist like you has to be MVC right?) is passing up dynamic CSS to be stuffed into the document head? Talk about muddling up the code!</p>
<p>I don&#8217;t see how this:<br />
<code><em>I love inline styles</em></code></p>
<p>Is worse than this:<br />
<code><br />
<em>I hate inline styles</em></code></p>
<p>In fact, that is just too ludicrous to even insinuate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
