<?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: Help verify some bustage?</title>
	<atom:link href="http://www.dria.org/wordpress/archives/2006/04/26/410/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dria.org/wordpress/archives/2006/04/26/410/</link>
	<description>intrepid girl reporter</description>
	<lastBuildDate>Wed, 10 Mar 2010 18:56:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Almanca tercüman</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-55826</link>
		<dc:creator>Almanca tercüman</dc:creator>
		<pubDate>Wed, 16 Jan 2008 20:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-55826</guid>
		<description>Cool thanks guys. I’ll test Bill’s proposed fix shortly...</description>
		<content:encoded><![CDATA[<p>Cool thanks guys. I’ll test Bill’s proposed fix shortly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Almanca tercüman</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-60042</link>
		<dc:creator>Almanca tercüman</dc:creator>
		<pubDate>Wed, 16 Jan 2008 20:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-60042</guid>
		<description>Cool thanks guys. I’ll test Bill’s proposed fix shortly...</description>
		<content:encoded><![CDATA[<p>Cool thanks guys. I’ll test Bill’s proposed fix shortly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dao</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-6307</link>
		<dc:creator>Dao</dc:creator>
		<pubDate>Wed, 31 May 2006 16:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-6307</guid>
		<description>Microsoft&#039;s Markus Mielke says the bug is fixed :)

http://design-noir.de/log/2006/04/internet-explorer-7-beta-2-veroeffentlicht/#comment-20</description>
		<content:encoded><![CDATA[<p>Microsoft&#8217;s Markus Mielke says the bug is fixed :)</p>
<p><a href="http://design-noir.de/log/2006/04/internet-explorer-7-beta-2-veroeffentlicht/#comment-20" rel="nofollow">http://design-noir.de/log/2006/04/internet-explorer-7-beta-2-veroeffentlicht/#comment-20</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dria</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3590</link>
		<dc:creator>dria</dc:creator>
		<pubDate>Thu, 27 Apr 2006 15:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3590</guid>
		<description>Dao: your float:left; fix works.  Thanks a million :)

&#039;Course I still have to test in all the other browsers...</description>
		<content:encoded><![CDATA[<p>Dao: your float:left; fix works.  Thanks a million :)</p>
<p>&#8216;Course I still have to test in all the other browsers&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dao</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3589</link>
		<dc:creator>Dao</dc:creator>
		<pubDate>Thu, 27 Apr 2006 15:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3589</guid>
		<description>IE7 has the same problem with my site&#039;s menu:  http://design-noir.de

IE6 had this too. That&#039;s why you added a workaround (_width: 1%). But IE7 won&#039;t recognize _width (which is correct).
#navigation #contenttypes li a { float: left; } would do the trick. But I suggest you leave it as it is and ask Microsoft to fix this ancient CSS1 bug.</description>
		<content:encoded><![CDATA[<p>IE7 has the same problem with my site&#8217;s menu:  <a href="http://design-noir.de" rel="nofollow">http://design-noir.de</a></p>
<p>IE6 had this too. That&#8217;s why you added a workaround (_width: 1%). But IE7 won&#8217;t recognize _width (which is correct).<br />
#navigation #contenttypes li a { float: left; } would do the trick. But I suggest you leave it as it is and ask Microsoft to fix this ancient CSS1 bug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MT</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3588</link>
		<dc:creator>MT</dc:creator>
		<pubDate>Thu, 27 Apr 2006 15:21:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3588</guid>
		<description>[sorry for reposting but some my text was handled as real anchor tags while it&#039;s not]

Just don&#039;t use height and line-height for [A] element inside navigation (in common case I usually use vertical padding instead of height + line-height).

But it&#039;s definitely a BUG of IE7b2 that DOESN&#039;T NEED for any workaround and should be reported to Microsoft and fixed by IE programmers before final IE7 ships.

P. S. Removing _width doesn&#039;t change nothing for me. But to make links clickable at its whole area (that probably is the aim of using _width: 1%) I usually use &quot;Star HTML&quot; hack with 1px height for [A] element. That hack now (since IE7 ignore it in strict mode) is a good way to address CSS rules (that are workaroud of bugs that are NOT longer takes place in IE7) separately for IE5-6 and IE7.</description>
		<content:encoded><![CDATA[<p>[sorry for reposting but some my text was handled as real anchor tags while it's not]</p>
<p>Just don&#8217;t use height and line-height for [A] element inside navigation (in common case I usually use vertical padding instead of height + line-height).</p>
<p>But it&#8217;s definitely a BUG of IE7b2 that DOESN&#8217;T NEED for any workaround and should be reported to Microsoft and fixed by IE programmers before final IE7 ships.</p>
<p>P. S. Removing _width doesn&#8217;t change nothing for me. But to make links clickable at its whole area (that probably is the aim of using _width: 1%) I usually use &#8220;Star HTML&#8221; hack with 1px height for [A] element. That hack now (since IE7 ignore it in strict mode) is a good way to address CSS rules (that are workaroud of bugs that are NOT longer takes place in IE7) separately for IE5-6 and IE7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MT</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3587</link>
		<dc:creator>MT</dc:creator>
		<pubDate>Thu, 27 Apr 2006 15:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3587</guid>
		<description>Just don&#039;t use height and line-height for &lt;a&gt; element inside navigation (in common case I usually use vertical padding instead of height + line-height).

But it&#039;s definitely a BUG of IE7b2 that DOESN&#039;T NEED for any workaround and should be reported to Microsoft and fixed by IE programmers before final IE7 ships.

P. S. Removing _width doesn&#039;t change nothing for me. But to make links clickable at its whole area (that probably is the aim of using _width: 1%) I usually use &quot;Star HTML&quot; hack with 1px height for &lt;/a&gt;&lt;a&gt; element. That hack now (since IE7 ignore it in strict mode) is a good way to address CSS rules (that are workaroud of bugs that are NOT longer takes place in IE7) separately for IE5-6 and IE7.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Just don&#8217;t use height and line-height for <a> element inside navigation (in common case I usually use vertical padding instead of height + line-height).</p>
<p>But it&#8217;s definitely a BUG of IE7b2 that DOESN&#8217;T NEED for any workaround and should be reported to Microsoft and fixed by IE programmers before final IE7 ships.</p>
<p>P. S. Removing _width doesn&#8217;t change nothing for me. But to make links clickable at its whole area (that probably is the aim of using _width: 1%) I usually use &#8220;Star HTML&#8221; hack with 1px height for </a><a> element. That hack now (since IE7 ignore it in strict mode) is a good way to address CSS rules (that are workaroud of bugs that are NOT longer takes place in IE7) separately for IE5-6 and IE7.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-60041</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Thu, 27 Apr 2006 14:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-60041</guid>
		<description>I think the _xxxxxx aer IEisms. Our Web designer once told me that alot of CSS hacks he uses make use of this &quot;feature&quot;. IE(6) will make use of _xxxx attributes while Firefox ignores them. He can then manage to get pages to behave identically (or close to it) on IE and FF.&lt;br&gt;&lt;br&gt;BOCICBW (but  of course, I could be wrong).&lt;br&gt;&lt;br&gt;L</description>
		<content:encoded><![CDATA[<p>I think the _xxxxxx aer IEisms. Our Web designer once told me that alot of CSS hacks he uses make use of this &#8220;feature&#8221;. IE(6) will make use of _xxxx attributes while Firefox ignores them. He can then manage to get pages to behave identically (or close to it) on IE and FF.</p>
<p>BOCICBW (but  of course, I could be wrong).</p>
<p>L</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3586</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Thu, 27 Apr 2006 13:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3586</guid>
		<description>I think the _xxxxxx aer IEisms. Our Web designer once told me that alot of CSS hacks he uses make use of this &quot;feature&quot;. IE(6) will make use of _xxxx attributes while Firefox ignores them. He can then manage to get pages to behave identically (or close to it) on IE and FF.

BOCICBW (but  of course, I could be wrong).

L</description>
		<content:encoded><![CDATA[<p>I think the _xxxxxx aer IEisms. Our Web designer once told me that alot of CSS hacks he uses make use of this &#8220;feature&#8221;. IE(6) will make use of _xxxx attributes while Firefox ignores them. He can then manage to get pages to behave identically (or close to it) on IE and FF.</p>
<p>BOCICBW (but  of course, I could be wrong).</p>
<p>L</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gérard Talbot</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3581</link>
		<dc:creator>Gérard Talbot</dc:creator>
		<pubDate>Thu, 27 Apr 2006 00:25:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3581</guid>
		<description>Deb, I confirm that there are layout problems of the navigation links when using the latest IE 7 beta 2 build 5346.5.

Note that the javascript console report CSS parsing errors:

#navigation #personal a {
	_width: 1%;
}

_width is not a CSS property.

Warning: Unknown property &#039;_width&#039;.  Declaration dropped.
Source File: http://developer.mozilla.org/css/base.css
Line: 194

Gérard</description>
		<content:encoded><![CDATA[<p>Deb, I confirm that there are layout problems of the navigation links when using the latest IE 7 beta 2 build 5346.5.</p>
<p>Note that the javascript console report CSS parsing errors:</p>
<p>#navigation #personal a {<br />
	_width: 1%;<br />
}</p>
<p>_width is not a CSS property.</p>
<p>Warning: Unknown property &#8216;_width&#8217;.  Declaration dropped.<br />
Source File: <a href="http://developer.mozilla.org/css/base.css" rel="nofollow">http://developer.mozilla.org/css/base.css</a><br />
Line: 194</p>
<p>Gérard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dria</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3580</link>
		<dc:creator>dria</dc:creator>
		<pubDate>Wed, 26 Apr 2006 21:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3580</guid>
		<description>Cool, thanks guys.  I&#039;ll test Bill&#039;s proposed fix shortly.  :)</description>
		<content:encoded><![CDATA[<p>Cool, thanks guys.  I&#8217;ll test Bill&#8217;s proposed fix shortly.  :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafael</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3578</link>
		<dc:creator>Rafael</dc:creator>
		<pubDate>Wed, 26 Apr 2006 21:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3578</guid>
		<description>Yup there&#039;s bustage.  Not sure if I can help with the fix.</description>
		<content:encoded><![CDATA[<p>Yup there&#8217;s bustage.  Not sure if I can help with the fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Mason</title>
		<link>http://www.dria.org/wordpress/archives/2006/04/26/410/comment-page-1/#comment-3577</link>
		<dc:creator>Bill Mason</dc:creator>
		<pubDate>Wed, 26 Apr 2006 20:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.dria.org/wordpress/archives/2006/04/26/410/#comment-3577</guid>
		<description>The problem is the display: block line in the #navigation #contenttypes li a definition in base.css.

Removing that line seems to fix it (playing with a locally saved copy of the page) in IE7b2 without breaking FF 1.5 or IE6.  That said, I don&#039;t know what older browser might be using that bit of code and be affected by losing it.</description>
		<content:encoded><![CDATA[<p>The problem is the display: block line in the #navigation #contenttypes li a definition in base.css.</p>
<p>Removing that line seems to fix it (playing with a locally saved copy of the page) in IE7b2 without breaking FF 1.5 or IE6.  That said, I don&#8217;t know what older browser might be using that bit of code and be affected by losing it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
