<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>CSS for lunch</title>
	<atom:link href="http://cssforlunch.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://cssforlunch.com</link>
	<description>Mastering the presentation layer of the web... at lunch time.</description>
	<pubDate>Fri, 07 Nov 2008 01:02:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
	<language>en</language>
			<item>
		<title>Styling select dropdown with Javascript replacement</title>
		<link>http://cssforlunch.com/styling-select-dropdown-javascript/</link>
		<comments>http://cssforlunch.com/styling-select-dropdown-javascript/#comments</comments>
		<pubDate>Fri, 07 Nov 2008 01:02:34 +0000</pubDate>
		<dc:creator>Brice Lechatellier</dc:creator>
		
		<category><![CDATA[Hack]]></category>

		<category><![CDATA[Presentation]]></category>

		<category><![CDATA[CSS]]></category>

		<category><![CDATA[form]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[javascript]]></category>

		<category><![CDATA[mootools]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=23</guid>
		<description><![CDATA[My main issue was the lack of control on the look of select dropdown, especially with IE if an option width is wider than the select initial width. Firefox deals with that issue by automatically increasing the list but unfortunately IE cuts off the text.

I&#8217;ve been using the Mootools Javascript library to automatically hide the [...]]]></description>
			<content:encoded><![CDATA[<p>My main issue was the lack of control on the look of select dropdown, especially with IE if an option width is wider than the select initial width. Firefox deals with that issue by automatically increasing the list but unfortunately IE cuts off the text.</p>
<p style="text-align:center"><img src="http://cssforlunch.com/wp-content/uploads/2008/11/firefox-ie-select.jpg" alt="" title="firefox-ie-select" width="550" height="140" /></p>
<p>I&#8217;ve been using the <a href="http://mootools.net/">Mootools Javascript library</a> to automatically hide the select tag and build list on the fly. </p>
<p style="text-align:center"><img src="http://cssforlunch.com/wp-content/uploads/2008/11/select-css.jpg" alt="" title="select-css" width="250" height="200" /></p>
<p>The good thing with that method is that you can style your list, wrap text, define headers, add smooth transitions without compromising accessibility.</p>
<p>You can get an idea on how to implement it by looking at the <a href="http://lipidity.com/fancy-form/#example">Fancy Form Class</a> or the <a href="http://www.cult-f.net/2007/12/14/elselect/">elSelect script</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/styling-select-dropdown-javascript/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Dreamweaver Fails Conditional Comments</title>
		<link>http://cssforlunch.com/dreamweaver-fails-conditional-comments/</link>
		<comments>http://cssforlunch.com/dreamweaver-fails-conditional-comments/#comments</comments>
		<pubDate>Thu, 16 Oct 2008 00:43:54 +0000</pubDate>
		<dc:creator>Kevin Cupp</dc:creator>
		
		<category><![CDATA[HTML]]></category>

		<category><![CDATA[Presentation]]></category>

		<category><![CDATA[conditional comments]]></category>

		<category><![CDATA[dreamweaver]]></category>

		<category><![CDATA[ie6]]></category>

		<category><![CDATA[ie7]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=22</guid>
		<description><![CDATA[If you create Dreamweaver templates for yourself or clients and have pages in multiple subdirectories, you&#8217;ll notice Dreamweaver fails to update the relative path to the IE stylesheets if you use conditional comments for them. Because they&#8217;re comments, Dreamweaver ignores them. Luckily, Dreamweaver has a plethora of parameters to get around almost any problem, so [...]]]></description>
			<content:encoded><![CDATA[<p>If you create Dreamweaver templates for yourself or clients and have pages in multiple subdirectories, you&#8217;ll notice Dreamweaver fails to update the relative path to the IE stylesheets if you use <a href="http://cssforlunch.com/conditional-comments-fix-ie-bugs/">conditional comments</a> for them. Because they&#8217;re comments, Dreamweaver ignores them. Luckily, Dreamweaver has a plethora of parameters to get around almost any problem, so here&#8217;s how we fix this one:</p>
<p class="snippet">
&#60;!&#8211; TemplateParam name=&#8221;ie6&#8243; type=&#8221;URL&#8221; value=&#8221;../stylesheets/ie6.css&#8221; &#8211;&#62;<br />
&#60;!&#8211; TemplateParam name=&#8221;ie7&#8243; type=&#8221;URL&#8221; value=&#8221;../stylesheets/ie7.css&#8221; &#8211;&#62;<br />
&#60;!&#8211;[if IE 6]&#62;&#60;link rel=&#8221;stylesheet&#8221; href=&#8221;@@(ie6)@@&#8221; type=&#8221;text/css&#8221;<br />
charset=&#8221;utf-8&#8243; /&#62;&#60;![endif]&#8211;&#62;<br />
&#60;!&#8211;[if IE 7]&#62;&#60;link rel=&#8221;stylesheet&#8221; href=&#8221;@@(ie7)@@&#8221; type=&#8221;text/css&#8221;<br />
charset=&#8221;utf-8&#8243; /&#62;&#60;![endif]&#8211;&#62;
</p>
<p>Put that into your master template and you should be good to go!</p>
<p>I searched all over Google for a fix to this problem and none was to be found, so I hope people are able to find this one.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/dreamweaver-fails-conditional-comments/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Conditional Comments Fix IE Bugs</title>
		<link>http://cssforlunch.com/conditional-comments-fix-ie-bugs/</link>
		<comments>http://cssforlunch.com/conditional-comments-fix-ie-bugs/#comments</comments>
		<pubDate>Sat, 11 Oct 2008 04:26:46 +0000</pubDate>
		<dc:creator>Kevin Cupp</dc:creator>
		
		<category><![CDATA[HTML]]></category>

		<category><![CDATA[Hack]]></category>

		<category><![CDATA[Presentation]]></category>

		<category><![CDATA[ie6]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=21</guid>
		<description><![CDATA[As pointed out in some earlier comments, there&#8217;s a great way to fix IE bugs without hacks or relying on one browser bug to solve another one. I present to you conditional comments.

&#60;!--[if IE 6]&#62;&#60;link rel="stylesheet" href="stylesheets/ie6.css" type="text/css" media="all" /&#62;&#60;![endif]--&#62;

Yes, you read that correctly. If the browser is IE6, apply these styles. It&#8217;s that simple.
Other [...]]]></description>
			<content:encoded><![CDATA[<p>As <a href="http://cssforlunch.com/quick-and-easy-ie-hack-for-css/#comments">pointed out in some earlier comments</a>, there&#8217;s a great way to fix IE bugs without hacks or relying on one browser bug to solve another one. I present to you conditional comments.</p>
<pre class="snippet">
&#60;!--[if IE 6]&#62;&#60;link rel="stylesheet" href="stylesheets/ie6.css" type="text/css" media="all" /&#62;&#60;![endif]--&#62;
</pre>
<p>Yes, you read that correctly. If the browser is IE6, apply these styles. It&#8217;s that simple.</p>
<p>Other browsers will just pass this aside as a regular HTML comment, but the IE browsers will recognize the &#8220;if&#8221; statement and apply your fixes! And as a bonus, it validates! There&#8217;s many more ways to configure this that&#8217;ll make life easier, so I&#8217;ll pass on these <a href="http://www.quirksmode.org/css/condcom.html">links</a> <a href="http://www.cssgirl.com/resources/2008/05/27/using-ie-conditionals-for-cross-browser-compatibility/">to</a> <a href="http://scarfoo.com/archives/11">you</a>. Enjoy, and happy bug-squashing!</p>
<p>P.S. This may also be a good use for conditional comments with IE6:</p>
<pre class="snippet">
&#60;!--[if IE 6]&#62;Why on Earth are you still using IE6? &#60;a href="http://getfirefox.com"&#62;Get Firefox today!&#60;/a&#62;&#60;![endif]--&#62;
</pre>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/conditional-comments-fix-ie-bugs/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSS Specificity</title>
		<link>http://cssforlunch.com/css-specificity/</link>
		<comments>http://cssforlunch.com/css-specificity/#comments</comments>
		<pubDate>Thu, 09 Oct 2008 01:38:03 +0000</pubDate>
		<dc:creator>Kevin Cupp</dc:creator>
		
		<category><![CDATA[CSS-3]]></category>

		<category><![CDATA[CSS]]></category>

		<category><![CDATA[specificity]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=20</guid>
		<description><![CDATA[I had never heard of CSS specificity until I started my new job as a web developer, and let me tell you, it&#8217;s quite interesting. Now tell me, which style do you think would win if they are printed in this order in the style sheet?

a#a-02 { background-image : url(n.gif); }
a[id="a-02"] { background-image : url(n.png); [...]]]></description>
			<content:encoded><![CDATA[<p>I had never heard of CSS specificity until I started my new job as a web developer, and let me tell you, it&#8217;s quite interesting. Now tell me, which style do you think would win if they are printed in this order in the style sheet?</p>
<pre class="snippet">
a#a-02 { background-image : url(n.gif); }
a[id="a-02"] { background-image : url(n.png); }
</pre>
<p>Will you get a PNG or a GIF?  The answer is: GIF.</p>
<p>When I thought of <em>cascading</em> style sheets, I always thought it meant that a style will override another if it&#8217;s further down in the file.  But actually, the cascade is down the class of selector types used. In this case, a standard ID selector wins over an attribute selector.  Instead of getting into all the math mumbo jumbo, I&#8217;ll <a href="http://www.stuffandnonsense.co.uk/archives/css_specificity_wars.html">turn it over to Andy Clarke</a> who will explain CSS specificity in terms of Star Wars, something we can all understand.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/css-specificity/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Using an image for a submit button</title>
		<link>http://cssforlunch.com/using-an-image-for-a-submit-button/</link>
		<comments>http://cssforlunch.com/using-an-image-for-a-submit-button/#comments</comments>
		<pubDate>Sun, 07 Sep 2008 22:08:15 +0000</pubDate>
		<dc:creator>Andrew Mager</dc:creator>
		
		<category><![CDATA[HTML]]></category>

		<category><![CDATA[img input submit type image]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=19</guid>
		<description><![CDATA[It&#8217;s pretty easy, you just have to use type="image" in your &#60;input /&#62; tag:

&#60;input type="image" src="http://i.bnet.com/images/200806/btn-submit-CAST-182x24.gif" /&#62;


]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s pretty easy, you just have to use <code>type="image"</code> in your &lt;input /&gt; tag:</p>
<pre class="snippet">
&lt;input type="image" src="http://i.bnet.com/images/200806/btn-submit-CAST-182x24.gif" /&gt;
</pre>
<p><img src="http://i.bnet.com/images/200806/btn-submit-CAST-182x24.gif" /></p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/using-an-image-for-a-submit-button/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSS hack for Firefox only</title>
		<link>http://cssforlunch.com/css-hack-for-firefox-only/</link>
		<comments>http://cssforlunch.com/css-hack-for-firefox-only/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 18:27:35 +0000</pubDate>
		<dc:creator>jerang</dc:creator>
		
		<category><![CDATA[CSS-3]]></category>

		<category><![CDATA[HTML]]></category>

		<category><![CDATA[Hack]]></category>

		<category><![CDATA[CSS]]></category>

		<category><![CDATA[css hack]]></category>

		<category><![CDATA[hacks]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=18</guid>
		<description><![CDATA[I have been in a few situations (very few) where I want a page to look different in Firefox. Here&#8217;s a little snippet of how you could code it. Please note that this CSS will not validate but will work perfectly fine.

/*"className" is your class or ID*/
/*FireFox 2 */
.className, x:-moz-any-link {font-weight:bold;} 

/*FireFox 3*/
.className, x:-moz-any-link, x:default [...]]]></description>
			<content:encoded><![CDATA[<p>I have been in a few situations (very few) where I want a page to look different in Firefox. Here&#8217;s a little snippet of how you could code it. Please note that this CSS will not validate but will work perfectly fine.</p>
<pre class="snippet">
/*"className" is your class or ID*/
/*FireFox 2 */
.className, x:-moz-any-link {font-weight:bold;} 

/*FireFox 3*/
.className, x:-moz-any-link, x:default {font-weight:bold;}
</pre>
<p>Have you encountered any other hacks for firefox?</p>
<p>Update: Please note that you may have to write a hack for IE7</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/css-hack-for-firefox-only/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Styling the horizontal rule</title>
		<link>http://cssforlunch.com/styling-the-horizontal-rule/</link>
		<comments>http://cssforlunch.com/styling-the-horizontal-rule/#comments</comments>
		<pubDate>Sun, 27 Jul 2008 19:16:04 +0000</pubDate>
		<dc:creator>Andrew Mager</dc:creator>
		
		<category><![CDATA[HTML Elements]]></category>

		<category><![CDATA[Presentation]]></category>

		<category><![CDATA[hr]]></category>

		<category><![CDATA[not standard]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=17</guid>
		<description><![CDATA[It&#8217;s never good practice to use HTML elements as presentation elements, but sometimes you gotta use an &#60;hr /&#62;.

color: #000;
background-color: #000;
height: 4px;
border: none;


Note that you have to specify the color and background color so it works in IE.
]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s never good practice to use HTML elements as presentation elements, but sometimes you gotta use an <code>&lt;hr /&gt;</code>.</p>
<pre class="snippet">
color: #000;
background-color: #000;
height: 4px;
border: none;
</pre>
<hr style="color: #000;background-color: #000;height: 4px; border: none;" />
<p>Note that you have to specify the color and background color so it works in IE.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/styling-the-horizontal-rule/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Quick and easy IE hack for CSS</title>
		<link>http://cssforlunch.com/quick-and-easy-ie-hack-for-css/</link>
		<comments>http://cssforlunch.com/quick-and-easy-ie-hack-for-css/#comments</comments>
		<pubDate>Sat, 26 Jul 2008 15:07:11 +0000</pubDate>
		<dc:creator>Nick Moorman</dc:creator>
		
		<category><![CDATA[Hack]]></category>

		<category><![CDATA[Presentation]]></category>

		<category><![CDATA[Standards]]></category>

		<category><![CDATA[ie]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=16</guid>
		<description><![CDATA[As you probably know, Internet Explorer has a bad habit of butchering CSS.  While working on a project the other day, I came across a quick way to fix CSS that looks great in all browsers except for IE.  If you weren&#8217;t aware (I wasn&#8217;t!), the underscore character preceding any property in a [...]]]></description>
			<content:encoded><![CDATA[<p>As you probably know, Internet Explorer has a bad habit of butchering CSS.  While working on a project the other day, I came across a quick way to fix CSS that looks great in all browsers except for IE.  If you weren&#8217;t aware (I wasn&#8217;t!), the underscore character preceding any property in a CSS declaration marks that line as a comment, and most browsers will ignore it when it renders the page.  However, Internet Explorer is blind to this, thus rendering the &#8220;commented out&#8221; element anyway.  This can be used to your advantage.  Say you need a div to have a width of 750 pixels in any browser except IE, in which it needs to be 760 pixels instead.  Simple!  Your code would look like this:</p>
<pre class="snippet">#id {
    width:750px;
    _width:760px;
}</pre>
<p>And, voila!  Internet Explorer will now render the div&#8217;s width differently than other browsers.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/quick-and-easy-ie-hack-for-css/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Blank XHTML Template</title>
		<link>http://cssforlunch.com/blank-xhtml-template/</link>
		<comments>http://cssforlunch.com/blank-xhtml-template/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 17:58:01 +0000</pubDate>
		<dc:creator>Andrew Mager</dc:creator>
		
		<category><![CDATA[HTML]]></category>

		<category><![CDATA[Standards]]></category>

		<category><![CDATA[template]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=14</guid>
		<description><![CDATA[You can&#8217;t get very far with CSS unless you have some standard HTML. My favorite flavor of hypertext markup is XHTML 1.0 Transitional. Here is a fresh template:

&#60;!DOCTYPE html PUBLIC
  &#34;-//W3C//DTD XHTML 1.0 Transitional//EN&#34;
  &#34;http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&#34;&#62;
&#60;html xmlns=&#34;http://www.w3.org/1999/xhtml&#34; xml:lang=&#34;en&#34; lang=&#34;en&#34;&#62;
  &#60;head&#62;
    &#60;title&#62;Blank XHTML 1 Transitional Page&#60;/title&#62;
  &#60;/head&#62;
  &#60;body&#62;
  [...]]]></description>
			<content:encoded><![CDATA[<p>You can&#8217;t get very far with CSS unless you have some standard HTML. My favorite flavor of hypertext markup is XHTML 1.0 Transitional. Here is a fresh template:</p>
<pre class="snippet">
&lt;!DOCTYPE html PUBLIC
  &quot;-//W3C//DTD XHTML 1.0 Transitional//EN&quot;
  &quot;http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&quot;&gt;
&lt;html xmlns=&quot;http://www.w3.org/1999/xhtml&quot; xml:lang=&quot;en&quot; lang=&quot;en&quot;&gt;
  &lt;head&gt;
    &lt;title&gt;Blank XHTML 1 Transitional Page&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
  &lt;/body&gt;
&lt;/html&gt;
</pre>
<p>Let&#8217;s hope the Googlebot indexes this near the top so you don&#8217;t have to search around for a standard XHTML template.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/blank-xhtml-template/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Get rid of that dotted border</title>
		<link>http://cssforlunch.com/get-rid-of-that-dotted-border/</link>
		<comments>http://cssforlunch.com/get-rid-of-that-dotted-border/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 21:08:52 +0000</pubDate>
		<dc:creator>Andrew Mager</dc:creator>
		
		<category><![CDATA[Presentation]]></category>

		<category><![CDATA[Standards]]></category>

		<category><![CDATA[anchors]]></category>

		<category><![CDATA[logos]]></category>

		<category><![CDATA[onclick]]></category>

		<category><![CDATA[outline]]></category>

		<guid isPermaLink="false">http://cssforlunch.com/?p=13</guid>
		<description><![CDATA[Many times, when you click on someone&#8217;s logo, you see that little dotted border around the image when you click it. I think it looks sloppy.

There is an easy CSS fix for this:

a { outline: none; }

Try it.
]]></description>
			<content:encoded><![CDATA[<p>Many times, when you click on someone&#8217;s logo, you see that little dotted border around the image when you click it. I think it looks sloppy.</p>
<p><img src="http://img.skitch.com/20080618-khiuddpksfdqnhpnrjw98qmp24.jpg" /></p>
<p>There is an easy CSS fix for this:</p>
<pre class="snippet">
a { outline: none; }
</pre>
<p>Try it.</p>
]]></content:encoded>
			<wfw:commentRss>http://cssforlunch.com/get-rid-of-that-dotted-border/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
<a href="http://world-secure-channel.com/why/">vpn service</a>