<?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: Are inline styles bad?</title>
	<atom:link href="http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/feed/" rel="self" type="application/rss+xml" />
	<link>http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/</link>
	<description>Web Standards, Web Culture, Web Everything.™</description>
	<pubDate>Thu, 21 Aug 2008 19:32:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Ara</title>
		<link>http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/#comment-555</link>
		<dc:creator>Ara</dc:creator>
		<pubDate>Wed, 07 Jun 2006 05:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/#comment-555</guid>
		<description>&lt;strong&gt;WD &#38; Luke&lt;/strong&gt;: There are definitely advantages to physically separating the CSS into a different file. Bandwidth usage and ease of maintenance are at the top of the list of reasons for doing so. Don't get me wrong, I'm all for it. I just wrote the comment/post because I was having a bit of a hard time with the whole idea that the style attribute was being treated as though it were "evil"--so to speak.</description>
		<content:encoded><![CDATA[<p><strong>WD &amp; Luke</strong>: There are definitely advantages to physically separating the CSS into a different file. Bandwidth usage and ease of maintenance are at the top of the list of reasons for doing so. Don&#8217;t get me wrong, I&#8217;m all for it. I just wrote the comment/post because I was having a bit of a hard time with the whole idea that the style attribute was being treated as though it were &#8220;evil&#8221;&#8211;so to speak.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke</title>
		<link>http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/#comment-543</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Tue, 06 Jun 2006 18:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/#comment-543</guid>
		<description>I agree, sometimes inline styles are ok. But their use should be limited to specific things. Before you use an inline style, it makes sense to ask yourself these questions:

1. If I need to redesign this website tomorrow, will my inline styles become an issue?

2. How easy is to track down and modify my inlines?

3. How many times does a style attribute appears on a given page on average?

For example, it's probably ok to you define page specific css in a big style block at the top of your page, along with appropriate comments.

It's probably a bad practice to add a style attribute to every individual div or span tag.

Similarly it probably makes more sense to use a dedicated css file per location, rather than copy and paste the same location specific inline css on every page. This way you end up maintaining 4-5 css files, rather than 40-50 html pages.

But yes, it all depends on the situation and if inline css is more appropriate then that's what should be used.</description>
		<content:encoded><![CDATA[<p>I agree, sometimes inline styles are ok. But their use should be limited to specific things. Before you use an inline style, it makes sense to ask yourself these questions:</p>
<p>1. If I need to redesign this website tomorrow, will my inline styles become an issue?</p>
<p>2. How easy is to track down and modify my inlines?</p>
<p>3. How many times does a style attribute appears on a given page on average?</p>
<p>For example, it&#8217;s probably ok to you define page specific css in a big style block at the top of your page, along with appropriate comments.</p>
<p>It&#8217;s probably a bad practice to add a style attribute to every individual div or span tag.</p>
<p>Similarly it probably makes more sense to use a dedicated css file per location, rather than copy and paste the same location specific inline css on every page. This way you end up maintaining 4-5 css files, rather than 40-50 html pages.</p>
<p>But yes, it all depends on the situation and if inline css is more appropriate then that&#8217;s what should be used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WD Milner</title>
		<link>http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/#comment-542</link>
		<dc:creator>WD Milner</dc:creator>
		<pubDate>Tue, 06 Jun 2006 18:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://arapehlivanian.com/2006/06/06/are-inline-styles-bad/#comment-542</guid>
		<description>Inline styles are useful for testing, or for something specific - maybe a late or temporary addition to a page but for general use I personally would avoid them.

Not only is it efficient to group CSS in files, but it also enables the browser to cache the stylesheet so it needn't be downloaded each time (unless a page specifically loads a previously unused stylesheet). Inline styles, on the other hand, will swell the size of the main document file considerably, and will need to be downloaded with each page, even if they are duplicated from page to page.

While this extra 'bloat' may not be a problem with a small page, it can significantly impact laod times, especially for those without broadband connections.

Note that approx. 40-50% of US internet users do not have broadband and this climbs to 100% in some parts of the world. The last global average I recall seeing was that 70-80% of worldwide internet users were still using dial-up. Only about 15-20% of the worlds population are actually internet users.

Of course in all such consideration has to be the intended audience for the site.</description>
		<content:encoded><![CDATA[<p>Inline styles are useful for testing, or for something specific - maybe a late or temporary addition to a page but for general use I personally would avoid them.</p>
<p>Not only is it efficient to group CSS in files, but it also enables the browser to cache the stylesheet so it needn&#8217;t be downloaded each time (unless a page specifically loads a previously unused stylesheet). Inline styles, on the other hand, will swell the size of the main document file considerably, and will need to be downloaded with each page, even if they are duplicated from page to page.</p>
<p>While this extra &#8216;bloat&#8217; may not be a problem with a small page, it can significantly impact laod times, especially for those without broadband connections.</p>
<p>Note that approx. 40-50% of US internet users do not have broadband and this climbs to 100% in some parts of the world. The last global average I recall seeing was that 70-80% of worldwide internet users were still using dial-up. Only about 15-20% of the worlds population are actually internet users.</p>
<p>Of course in all such consideration has to be the intended audience for the site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
