<?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 Hacks inside CSS</title>
	<atom:link href="http://www.onyx-design.net/css/css-hacks-inside-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onyx-design.net/css/css-hacks-inside-css/</link>
	<description>A weblog about webdesign, webdevelopment, css, php and other webrelated topics.</description>
	<lastBuildDate>Tue, 01 Jun 2010 09:29:28 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: CSS coding for cross browser compatibility &#124; Onyx Design Weblog</title>
		<link>http://www.onyx-design.net/css/css-hacks-inside-css/comment-page-1/#comment-273</link>
		<dc:creator>CSS coding for cross browser compatibility &#124; Onyx Design Weblog</dc:creator>
		<pubDate>Mon, 12 May 2008 10:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.onyx-design.net/weblog2/featured/css-hacks-inside-css/#comment-273</guid>
		<description>[...] CSS hacks inside CSS     //digg_bgcolor = &#039;#ff9900&#039;; digg_skin = &#039;compact&#039;; digg_window = &#039;new&#039;;    submit_url = &#039;http://www.onyx-design.net/weblog2/css/css-coding-for-cross-browser-compatibility/&#039;;      This entry was posted on Monday, May 12th, 2008 at 11:11 am and is filed under Browsers, CSS. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. [...]</description>
		<content:encoded><![CDATA[<p>[...] <acronym title="Cascading Style Sheets">CSS</acronym> hacks inside <acronym title="Cascading Style Sheets">CSS</acronym>     //digg_bgcolor = &#8216;#ff9900&#8242;; digg_skin = &#8216;compact&#8217;; digg_window = &#8216;new&#8217;;    submit_url = &#8216;http://www.onyx-design.net/weblog2/css/css-coding-for-cross-browser-compatibility/&#8217;;      This entry was posted on Monday, May 12th, 2008 at 11:11 am and is filed under Browsers, <acronym title="Cascading Style Sheets">CSS</acronym>. You can follow any responses to this entry through the <acronym title="Really Simple Syndication">RSS</acronym> 2.0 feed. You can leave a response, or trackback from your own site. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Make your site cross browser compatible in 5 steps &#124; Onyx Design Weblog</title>
		<link>http://www.onyx-design.net/css/css-hacks-inside-css/comment-page-1/#comment-46</link>
		<dc:creator>Make your site cross browser compatible in 5 steps &#124; Onyx Design Weblog</dc:creator>
		<pubDate>Sun, 16 Mar 2008 17:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.onyx-design.net/weblog2/featured/css-hacks-inside-css/#comment-46</guid>
		<description>[...] CSS hacks In-CSSIf you don&#8217;t want to edit your HTML file with conditional comments, see my article about CSS hacks inside your CSS file. [...]</description>
		<content:encoded><![CDATA[<p>[...] <acronym title="Cascading Style Sheets">CSS</acronym> hacks In-CSSIf you don&#8217;t want to edit your <acronym title="HyperText Markup Language">HTML</acronym> file with conditional comments, see my article about <acronym title="Cascading Style Sheets">CSS</acronym> hacks inside your <acronym title="Cascading Style Sheets">CSS</acronym> file. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nlife</title>
		<link>http://www.onyx-design.net/css/css-hacks-inside-css/comment-page-1/#comment-31</link>
		<dc:creator>Nlife</dc:creator>
		<pubDate>Sun, 10 Feb 2008 11:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.onyx-design.net/weblog2/featured/css-hacks-inside-css/#comment-31</guid>
		<description>I still prefer conditional comments, I think it&#039;s easier: one tag for your seperate CSS in two comment &#039;tags&#039;.

If you use this CSS, you don&#039;t always know what the result will be (with different browsers) and you can also make mistakes with typing CSS hacks. And often I also forget what the purpose of the code was, but you can always add comments in your CSS.</description>
		<content:encoded><![CDATA[<p>I still prefer conditional comments, I think it&#8217;s easier: one tag for your seperate <acronym title="Cascading Style Sheets">CSS</acronym> in two comment &#8216;tags&#8217;.</p>
<p>If you use this <acronym title="Cascading Style Sheets">CSS</acronym>, you don&#8217;t always know what the result will be (with different browsers) and you can also make mistakes with typing <acronym title="Cascading Style Sheets">CSS</acronym> hacks. And often I also forget what the purpose of the code was, but you can always add comments in your <acronym title="Cascading Style Sheets">CSS</acronym>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.onyx-design.net/css/css-hacks-inside-css/comment-page-1/#comment-30</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 09 Feb 2008 21:45:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.onyx-design.net/weblog2/featured/css-hacks-inside-css/#comment-30</guid>
		<description>@jbj
That first one sounds good ;) Thanks, maybe I should include it in my article.
But I don&#039;t see the benefits of the second one, because it won&#039;t validate.
Thanks for your comment!</description>
		<content:encoded><![CDATA[<p>@jbj<br />
That first one sounds good <img src='http://www.onyx-design.net/weblog2/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  Thanks, maybe I should include it in my article.<br />
But I don&#8217;t see the benefits of the second one, because it won&#8217;t validate.<br />
Thanks for your comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbj</title>
		<link>http://www.onyx-design.net/css/css-hacks-inside-css/comment-page-1/#comment-29</link>
		<dc:creator>jbj</dc:creator>
		<pubDate>Sat, 09 Feb 2008 18:27:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.onyx-design.net/weblog2/featured/css-hacks-inside-css/#comment-29</guid>
		<description>Another good way to hide anything to IE6 is to use the !important directive:

width: 200px !important; /*Visible by any browsers, IE6 exepted*/
width: 150px; /*Visible by IE6, other browsers will not apply due to the !important directive.*/

The following hacks may be useful, althout, yur css will not validate.

_width:200px; /*Only IE6 sees it*/
.width: 300px; /*Only IE7 sees it (notice the dot before the property name! */


Greetings from Belgium;
jbj</description>
		<content:encoded><![CDATA[<p>Another good way to hide anything to <acronym title="Internet Explorer 6">IE6</acronym> is to use the !important directive:</p>
<p>width: 200px !important; /*Visible by any browsers, <acronym title="Internet Explorer 6">IE6</acronym> exepted*/<br />
width: 150px; /*Visible by <acronym title="Internet Explorer 6">IE6</acronym>, other browsers will not apply due to the !important directive.*/</p>
<p>The following hacks may be useful, althout, yur css will not validate.</p>
<p>_width:200px; /*Only <acronym title="Internet Explorer 6">IE6</acronym> sees it*/<br />
.width: 300px; /*Only IE7 sees it (notice the dot before the property name! */</p>
<p>Greetings from Belgium;<br />
jbj</p>
]]></content:encoded>
	</item>
</channel>
</rss>
