<?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: CSS Negotiation and a Sanity Saving Shortcut</title>
	<atom:link href="http://leftjustified.net/journal/2004/10/07/css-negotiation/feed/" rel="self" type="application/rss+xml" />
	<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/</link>
	<description>In a few words, explain what this weblog is about.</description>
	<lastBuildDate>Wed, 11 Feb 2009 06:59:21 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew</title>
		<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1996</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sun, 01 May 2005 03:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1996</guid>
		<description>Yes, the star is the &#039;universal selector&#039; -- it&#039;s a wildcard which selects all elements :)</description>
		<content:encoded><![CDATA[<p>Yes, the star is the &#8216;universal selector&#8217; &#8212; it&#8217;s a wildcard which selects all elements <img src='http://leftjustified.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fambizzari</title>
		<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1992</link>
		<dc:creator>fambizzari</dc:creator>
		<pubDate>Fri, 29 Apr 2005 00:46:52 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1992</guid>
		<description>* { padding:0; margin:0; } 

Should the star be included as well?</description>
		<content:encoded><![CDATA[<p>* { padding:0; margin:0; } </p>
<p>Should the star be included as well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1703</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 15 Apr 2005 15:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1703</guid>
		<description>One more big thanks for the padding: 0 margin: 0 suggestion. I have spent countless hours trying to get elements to align correctly across the major browsers -- which is akin to hearding a bunch of cats. This simple trick will make life so much easier!
&lt;p /&gt;
As far as browser support goes -- I know two estremely wealthy people who use ancient hardware and never bother to upgrade their browsers. They are too busy making money to bother with upgrading anything, but they have the cash to buy almost anything and they do shop online. They may be only one in a million, but do you want to turn away a deep pocket customer like that?</description>
		<content:encoded><![CDATA[<p>One more big thanks for the padding: 0 margin: 0 suggestion. I have spent countless hours trying to get elements to align correctly across the major browsers &#8212; which is akin to hearding a bunch of cats. This simple trick will make life so much easier!</p>
<p />
As far as browser support goes &#8212; I know two estremely wealthy people who use ancient hardware and never bother to upgrade their browsers. They are too busy making money to bother with upgrading anything, but they have the cash to buy almost anything and they do shop online. They may be only one in a million, but do you want to turn away a deep pocket customer like that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland H.</title>
		<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1575</link>
		<dc:creator>Roland H.</dc:creator>
		<pubDate>Wed, 23 Mar 2005 20:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1575</guid>
		<description>Conditional comments can in fact be used to detect any specific version of MSIE.  This technique, I believe, can be used to replace the more ugly CSS hack you suggest for differentiating between MSIE 5 and MSIE 5.5:
&lt;a href=&quot;http://www.javascriptkit.com/howto/cc2.shtml&quot;&gt;www.javascriptkit.com/howto/cc2.shtml&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Conditional comments can in fact be used to detect any specific version of MSIE.  This technique, I believe, can be used to replace the more ugly CSS hack you suggest for differentiating between MSIE 5 and MSIE 5.5:<br />
<a href="http://www.javascriptkit.com/howto/cc2.shtml">http://www.javascriptkit.com/howto/cc2.shtml</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Davidson</title>
		<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1078</link>
		<dc:creator>Brian Davidson</dc:creator>
		<pubDate>Sat, 05 Mar 2005 19:25:29 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-1078</guid>
		<description>I suppose in this age of hack usage to try to serve different css to dodgy (and in some cases, not-so dodgy) browsers, it may seem almost blasphemous to say this, but I don&#039;t use hacks.
Of any kind.
At all.

I (accidently) prevent NN4 from using my CSS by linking to the CSS file with a comma-separated media list but that is not really a hack, just CSS-compliant, and reduces the number of lines in my HTML file.

As a result I don&#039;t need to worry about which hack goes with which browser, or inventing new hacks as other, more-compliant, browsers become available. Also, if you have NN4 or IE5.0 hacks, will you remove them as these browsers become less popular? At what level will you do so? When their usage drops below 10%? 5%? Or will your site always have the box model hack because there might just be one user in 10 million still using this browser in 2015?

I let the web be the web. I design according to recommendations in the knowledge that a compliant browser won&#039;t break my site (and this browser is coming. Soon. Maybe...)</description>
		<content:encoded><![CDATA[<p>I suppose in this age of hack usage to try to serve different css to dodgy (and in some cases, not-so dodgy) browsers, it may seem almost blasphemous to say this, but I don&#8217;t use hacks.<br />
Of any kind.<br />
At all.</p>
<p>I (accidently) prevent NN4 from using my CSS by linking to the CSS file with a comma-separated media list but that is not really a hack, just CSS-compliant, and reduces the number of lines in my HTML file.</p>
<p>As a result I don&#8217;t need to worry about which hack goes with which browser, or inventing new hacks as other, more-compliant, browsers become available. Also, if you have NN4 or IE5.0 hacks, will you remove them as these browsers become less popular? At what level will you do so? When their usage drops below 10%? 5%? Or will your site always have the box model hack because there might just be one user in 10 million still using this browser in 2015?</p>
<p>I let the web be the web. I design according to recommendations in the knowledge that a compliant browser won&#8217;t break my site (and this browser is coming. Soon. Maybe&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben scott</title>
		<link>http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-435</link>
		<dc:creator>ben scott</dc:creator>
		<pubDate>Fri, 28 Jan 2005 12:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://leftjustified.net/journal/2004/10/07/css-negotiation/#comment-435</guid>
		<description>Think it is good when writing about a catch all css article to mention something about fonts set up.

From what I heard from someone else a good trick is to set the font size to 100% and then make sure all other font sizes dont go under 0.7 ems. As long as inheritance problems aren&#039;t coming from a conatiner DIV tag giving 0.7ems and the 0.7ems of that for the P tage you shouldn&#039;t ever get any problems.

also it might be nice to set a page default font in the body tag.</description>
		<content:encoded><![CDATA[<p>Think it is good when writing about a catch all css article to mention something about fonts set up.</p>
<p>From what I heard from someone else a good trick is to set the font size to 100% and then make sure all other font sizes dont go under 0.7 ems. As long as inheritance problems aren&#8217;t coming from a conatiner DIV tag giving 0.7ems and the 0.7ems of that for the P tage you shouldn&#8217;t ever get any problems.</p>
<p>also it might be nice to set a page default font in the body tag.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
