<?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: IE “phone-book”</title>
	<atom:link href="http://aplus.rs/css/ie-phone-book/feed/" rel="self" type="application/rss+xml" />
	<link>http://aplus.rs/css/ie-phone-book/</link>
	<description>aplus.rs</description>
	<lastBuildDate>Mon, 30 Jan 2012 18:38:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Screwtape</title>
		<link>http://aplus.rs/css/ie-phone-book/comment-page-1/#comment-3383</link>
		<dc:creator>Screwtape</dc:creator>
		<pubDate>Fri, 13 May 2005 02:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.aplus.co.yu/?p=8#comment-3383</guid>
		<description>I note that the CSS2.1 spec says &quot;Other stacking contexts are generated by any positioned element (including relatively positioned elements) having a computed value of &#039;z-index&#039; other than &#039;auto&#039;&quot; (http://www.w3.org/TR/CSS21/visuren.html#q30) which leads me to believe that ordinary elements with position: relative should *not* establish new stacking contexts, which means that although IE adheres to the murky text of CSS2, Gecko adheres to the clearer intent of CSS2.1.

The poor IE team, they can&#039;t seem to get anything right!</description>
		<content:encoded><![CDATA[<p>I note that the CSS2.1 spec says “Other stacking contexts are generated by any positioned element (including relatively positioned elements) having a computed value of ‘z-index’ other than ‘auto’” (<a href="http://www.w3.org/TR/CSS21/visuren.html#q30" rel="nofollow">http://www.w3.org/TR/CSS21/visuren.html#q30</a>) which leads me to believe that ordinary elements with position: relative should *not* establish new stacking contexts, which means that although IE adheres to the murky text of CSS2, Gecko adheres to the clearer intent of CSS2.1.</p>
<p>The poor IE team, they can’t seem to get anything right!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Edwards</title>
		<link>http://aplus.rs/css/ie-phone-book/comment-page-1/#comment-6</link>
		<dc:creator>James Edwards</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.aplus.co.yu/?p=8#comment-6</guid>
		<description>You can solve this issue by having the &lt;li&gt; &quot;position:static&quot; and the &lt;a&gt; &quot;position:relative&quot;.  This does of course of change the origin of the submenu, and therefore requires the menu positioning to be done in javascript.  Works though..
</description>
		<content:encoded><![CDATA[<p>You can solve this issue by having the &lt;li&gt; “position:static” and the &lt;a&gt; “position:relative”.  This does of course of change the origin of the submenu, and therefore requires the menu positioning to be done in javascript.  Works though..</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)

Served from: aplus.rs @ 2012-02-07 18:52:00 -->
