<?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: Standards-Friendly IE Button Width Fix</title>
	<atom:link href="http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/</link>
	<description>Design wisdom in red and grey.</description>
	<lastBuildDate>Fri, 03 Feb 2012 17:03:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Darkimmortal</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-30621</link>
		<dc:creator>Darkimmortal</dc:creator>
		<pubDate>Tue, 12 Feb 2008 23:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-30621</guid>
		<description>Far, far simpler fix that I can confirm works in both IE6 and IE7, requires no HTML modification and as far as I can tell, doesn&#039;t affect other input boxes that don&#039;t have a defined width (which they should have anyway).

If other input boxes get messed up, just use a class on the top hack (IE6).


----------------------
THE HACK:
----------------------

/* IE6 */
* html input {
	overflow: visible; 
	width: 1px;
}

/* IE7 */
*+html input {
	overflow: visible; 
}</description>
		<content:encoded><![CDATA[<p>Far, far simpler fix that I can confirm works in both IE6 and IE7, requires no HTML modification and as far as I can tell, doesn&#8217;t affect other input boxes that don&#8217;t have a defined width (which they should have anyway).</p>
<p>If other input boxes get messed up, just use a class on the top hack (IE6).</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
THE HACK:<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>/* IE6 */<br />
* html input {<br />
	overflow: visible;<br />
	width: 1px;<br />
}</p>
<p>/* IE7 */<br />
*+html input {<br />
	overflow: visible;<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brownspank</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-30128</link>
		<dc:creator>Brownspank</dc:creator>
		<pubDate>Tue, 23 Oct 2007 13:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-30128</guid>
		<description>&lt;strong&gt;Andy:&lt;/strong&gt; Hmmm, your fix doesn&#039;t seem to work for me. It still produces extra space to the right of the cell it&#039;s in. Anyway, more information on this can be found in &lt;a href=&quot;/sixthings/2006/05/12/an-even-better-ie-button-width-fix/&quot; rel=&quot;nofollow&quot;&gt;An Even Better IE Button Width Fix&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p><strong>Andy:</strong> Hmmm, your fix doesn&#8217;t seem to work for me. It still produces extra space to the right of the cell it&#8217;s in. Anyway, more information on this can be found in <a href="/sixthings/2006/05/12/an-even-better-ie-button-width-fix/" rel="nofollow">An Even Better IE Button Width Fix</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Towler</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-30127</link>
		<dc:creator>Andy Towler</dc:creator>
		<pubDate>Tue, 23 Oct 2007 12:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-30127</guid>
		<description>It doesn&#039;t work when inside a table cell on IE7. However, if you just ensure that your button has width:auto and overflow:visible, and IS ENCLOSED IN A FLOATED ELEMENT within the table cell, everything is fine. No need for conditional comments or CSS hacks. Tested on FF2, Opera9, IE6, IE7.

If floating mucks up your layout, put a clear on the next element (but not the button!).</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t work when inside a table cell on IE7. However, if you just ensure that your button has width:auto and overflow:visible, and IS ENCLOSED IN A FLOATED ELEMENT within the table cell, everything is fine. No need for conditional comments or CSS hacks. Tested on FF2, Opera9, IE6, IE7.</p>
<p>If floating mucks up your layout, put a clear on the next element (but not the button!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An Even Better IE Button Width Fix at SixThings</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-3670</link>
		<dc:creator>An Even Better IE Button Width Fix at SixThings</dc:creator>
		<pubDate>Thu, 09 Nov 2006 08:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-3670</guid>
		<description>[...] Just recently, Peter replied to that article, proposing an alternative solution that did away with conditional statements. This would mean that you could include the CSS fix in your main stylesheet (and not in the HTML with the conditional comment, or in a separate stylesheet for just IE fixes). [...]</description>
		<content:encoded><![CDATA[<p>[...] Just recently, Peter replied to that article, proposing an alternative solution that did away with conditional statements. This would mean that you could include the CSS fix in your main stylesheet (and not in the HTML with the conditional comment, or in a separate stylesheet for just IE fixes). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brownspank</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-197</link>
		<dc:creator>Brownspank</dc:creator>
		<pubDate>Fri, 12 May 2006 08:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-197</guid>
		<description>&lt;strong&gt;Peter:&lt;/strong&gt; Actually, if you&#039;re filtering out IE instead of providing conditional statements, it should be the other way around, like so:
&lt;pre&gt;input.button {
    padding: 0 .25em;
    width: 0;
    overflow:visible;
}

input.button[class] { /*ie ignores [class]*/
    width: auto;
}&lt;/pre&gt;

&lt;a href=&quot;http://www.brownbatterystudios.com/sixthings/2006/05/12/an-even-better-ie-button-width-fix/&quot; rel=&quot;nofollow&quot;&gt;I had to write it down&lt;/a&gt;, for future usage. :)

I have to admit, I haven&#039;t seen widespread use of selector variants for filtering out specific browsers, which is pure genius! Let&#039;s just hope that when IE7 Final comes out, it&#039;ll do away with the nasty button width quirk altogether.</description>
		<content:encoded><![CDATA[<p><strong>Peter:</strong> Actually, if you&#8217;re filtering out IE instead of providing conditional statements, it should be the other way around, like so:</p>
<pre>input.button {
    padding: 0 .25em;
    width: 0;
    overflow:visible;
}

input.button[class] { /*ie ignores [class]*/
    width: auto;
}</pre>
<p><a href="http://www.brownbatterystudios.com/sixthings/2006/05/12/an-even-better-ie-button-width-fix/" rel="nofollow">I had to write it down</a>, for future usage. :)</p>
<p>I have to admit, I haven&#8217;t seen widespread use of selector variants for filtering out specific browsers, which is pure genius! Let&#8217;s just hope that when IE7 Final comes out, it&#8217;ll do away with the nasty button width quirk altogether.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-196</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 11 May 2006 16:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-196</guid>
		<description>How about this instead of conditionally showing style blocks?

.button[class]  /*ie ignores [class]*/
 {
    padding: 0 .25em;
    width: auto;
    overflow:visible;
}
.button {
    width: 0;
}
</description>
		<content:encoded><![CDATA[<p>How about this instead of conditionally showing style blocks?</p>
<p>.button[class]  /*ie ignores [class]*/<br />
 {<br />
    padding: 0 .25em;<br />
    width: auto;<br />
    overflow:visible;<br />
}<br />
.button {<br />
    width: 0;<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brownspank</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-5</link>
		<dc:creator>Brownspank</dc:creator>
		<pubDate>Sun, 19 Feb 2006 04:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-5</guid>
		<description>&lt;strong&gt;Derk:&lt;/strong&gt; A boycott is very much possible, which &lt;em&gt;might&lt;/em&gt; be why IE7 is taking a hint from Firefox with regards to functionality and standards-compliance. ;)</description>
		<content:encoded><![CDATA[<p><strong>Derk:</strong> A boycott is very much possible, which <em>might</em> be why IE7 is taking a hint from Firefox with regards to functionality and standards-compliance. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derk</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-4</link>
		<dc:creator>Derk</dc:creator>
		<pubDate>Sat, 18 Feb 2006 12:03:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-4</guid>
		<description>Well, we could at least minimize the support. It&#039;s ridiculous to force a person adjusting a design because of one stupid browser.

Boycotting would be practical though, if simply everyone would. I hope IE7 will bring some relief, though their BETA was, again, complete crap.</description>
		<content:encoded><![CDATA[<p>Well, we could at least minimize the support. It&#8217;s ridiculous to force a person adjusting a design because of one stupid browser.</p>
<p>Boycotting would be practical though, if simply everyone would. I hope IE7 will bring some relief, though their BETA was, again, complete crap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brownspank</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-3</link>
		<dc:creator>Brownspank</dc:creator>
		<pubDate>Sat, 18 Feb 2006 04:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-3</guid>
		<description>&lt;strong&gt;Derk:&lt;/strong&gt; Interesting, yes. Practical, not quite. A majority of people still use Internet Explorer for their web activities, hence the need for fixes that ensure visual consistency.</description>
		<content:encoded><![CDATA[<p><strong>Derk:</strong> Interesting, yes. Practical, not quite. A majority of people still use Internet Explorer for their web activities, hence the need for fixes that ensure visual consistency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derk</title>
		<link>http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-2</link>
		<dc:creator>Derk</dc:creator>
		<pubDate>Fri, 17 Feb 2006 17:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownbatterystudios.com/sixthings/2006/02/14/standards-friendly-ie-button-width-fix/#comment-2</guid>
		<description>Wouldn&#039;t it be more interesting to just boycot the whole IE scene instead of trying to find fixes for them?</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t it be more interesting to just boycot the whole IE scene instead of trying to find fixes for them?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

