<?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: Z-Index And The CSS Stack: Which Element Displays First?</title>
	<atom:link href="http://www.vanseodesign.com/css/css-stack-z-index/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vanseodesign.com/css/css-stack-z-index/</link>
	<description>Helping you build search engine friendly websites</description>
	<lastBuildDate>Tue, 27 Jul 2010 18:07:45 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</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: Steven Bradley</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-51370</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Tue, 09 Feb 2010 00:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-51370</guid>
		<description>Thanks for pointing that out. I wasn&#039;t aware of the issue. Do you know if it&#039;s specific to certain browsers or is it a general issue affecting all browsers?

As far as I know z-index should work the same on statically positioned elements. Should being the operative word. The spec says it should work at least.

If you can offer more details or point me somewhere that talks about this more it would be appreciated.

Thanks again.</description>
		<content:encoded><![CDATA[<p>Thanks for pointing that out. I wasn&#8217;t aware of the issue. Do you know if it&#8217;s specific to certain browsers or is it a general issue affecting all browsers?</p>
<p>As far as I know z-index should work the same on statically positioned elements. Should being the operative word. The spec says it should work at least.</p>
<p>If you can offer more details or point me somewhere that talks about this more it would be appreciated.</p>
<p>Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noone</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-51325</link>
		<dc:creator>noone</dc:creator>
		<pubDate>Mon, 08 Feb 2010 06:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-51325</guid>
		<description>It may be worth mentioning that declaring position:static on an element does not register its z-index correctly.</description>
		<content:encoded><![CDATA[<p>It may be worth mentioning that declaring position:static on an element does not register its z-index correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-49432</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Mon, 18 Jan 2010 21:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-49432</guid>
		<description>Thanks Mark. I&#039;ll have to test some code across browsers. The code in the post is more from memory than testing so it&#039;s always possible I got it wrong and your explanation does make a lot of sense.

I had thought the code I used would cause the problem, but now I&#039;m thinking you&#039;re right and it&#039;s the z-index: auto being treated as z-index: 1 in IE that causes the problem. Maybe I was thinking more about the fix, which would be to increase the z-index on the div to be more than the z-index on the image. Of course that assumes it would still work like you want in other browsers.

It definitely gets confusing. You can read through the specs and even test different code and sometimes you still have no idea why something is happening.</description>
		<content:encoded><![CDATA[<p>Thanks Mark. I&#8217;ll have to test some code across browsers. The code in the post is more from memory than testing so it&#8217;s always possible I got it wrong and your explanation does make a lot of sense.</p>
<p>I had thought the code I used would cause the problem, but now I&#8217;m thinking you&#8217;re right and it&#8217;s the z-index: auto being treated as z-index: 1 in IE that causes the problem. Maybe I was thinking more about the fix, which would be to increase the z-index on the div to be more than the z-index on the image. Of course that assumes it would still work like you want in other browsers.</p>
<p>It definitely gets confusing. You can read through the specs and even test different code and sometimes you still have no idea why something is happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Spitz</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-49297</link>
		<dc:creator>Mark Spitz</dc:creator>
		<pubDate>Sat, 16 Jan 2010 20:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-49297</guid>
		<description>I think the point you make about errors with IE browsers may be misleading and here&#039;s my understanding about why:

In the example snippet you provide, all browsers correctly place the image above the paragraph because the  (with paragraph&#039;s inside) and the image share the same stacking context. It&#039;s as though there is a a parent  enclosing all your code with any z-index value. The value doesn&#039;t matter because this parent  is setting the stacking context for ALL its descendants.

Okay, what we need then to demonstrate IE&#039;s typically wayward behaviour is a real parent  and let&#039;s assume it is given a z-index of 69 (any old number will do).

If you leave the rest of your code snippet unchanged then all browsers will continue to place the image above the text.

But now remove the z-index from the div with the paragraph. This forces browsers to give that div the default value for z-index which is &quot;auto&quot;.

It is this that IE gets wrong. It treats auto as though it were a value of 1 and (crucially) also establishes a new stacking context. The div and the image now no longer share the same stacking context as far as IE is concerned. This leaves the image above the paragraph.

Standards compliant browsers will treat the auto attribute correctly meaning that it inherits the z-index of its parent and NO new stacking context is created. The result then is the text above the image.

Confusing isn&#039;t it! And sometimes the act of trying to explain can confuse further. In case I have done that then try a simpler analysis to show IE&#039;s mistreatment of &quot;auto&quot; and change the z-index value on your  from zero to auto and check it out.</description>
		<content:encoded><![CDATA[<p>I think the point you make about errors with IE browsers may be misleading and here&#8217;s my understanding about why:</p>
<p>In the example snippet you provide, all browsers correctly place the image above the paragraph because the  (with paragraph&#8217;s inside) and the image share the same stacking context. It&#8217;s as though there is a a parent  enclosing all your code with any z-index value. The value doesn&#8217;t matter because this parent  is setting the stacking context for ALL its descendants.</p>
<p>Okay, what we need then to demonstrate IE&#8217;s typically wayward behaviour is a real parent  and let&#8217;s assume it is given a z-index of 69 (any old number will do).</p>
<p>If you leave the rest of your code snippet unchanged then all browsers will continue to place the image above the text.</p>
<p>But now remove the z-index from the div with the paragraph. This forces browsers to give that div the default value for z-index which is &#8220;auto&#8221;.</p>
<p>It is this that IE gets wrong. It treats auto as though it were a value of 1 and (crucially) also establishes a new stacking context. The div and the image now no longer share the same stacking context as far as IE is concerned. This leaves the image above the paragraph.</p>
<p>Standards compliant browsers will treat the auto attribute correctly meaning that it inherits the z-index of its parent and NO new stacking context is created. The result then is the text above the image.</p>
<p>Confusing isn&#8217;t it! And sometimes the act of trying to explain can confuse further. In case I have done that then try a simpler analysis to show IE&#8217;s mistreatment of &#8220;auto&#8221; and change the z-index value on your  from zero to auto and check it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-45937</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Thu, 10 Dec 2009 06:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-45937</guid>
		<description>Thanks Diane.</description>
		<content:encoded><![CDATA[<p>Thanks Diane.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-45875</link>
		<dc:creator>Diane</dc:creator>
		<pubDate>Wed, 09 Dec 2009 14:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-45875</guid>
		<description>Excellent article Steve! :)</description>
		<content:encoded><![CDATA[<p>Excellent article Steve! <img src='http://www.vanseodesign.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 110+ Incredible Community Links for Web Designers and Develovers&#160;&#124;&#160;tripwire magazine</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-45536</link>
		<dc:creator>110+ Incredible Community Links for Web Designers and Develovers&#160;&#124;&#160;tripwire magazine</dc:creator>
		<pubDate>Sun, 06 Dec 2009 06:20:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-45536</guid>
		<description>[...] Z-Index And The CSS Stack: Which Element Displays First? [...]</description>
		<content:encoded><![CDATA[<p>[...] Z-Index And The CSS Stack: Which Element Displays First? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Z-Index And The CSS Stack: Which Element Displays First? &#124; Design Newz</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-45472</link>
		<dc:creator>Z-Index And The CSS Stack: Which Element Displays First? &#124; Design Newz</dc:creator>
		<pubDate>Sat, 05 Dec 2009 16:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-45472</guid>
		<description>[...] Z-Index And The CSS Stack: Which Element Displays First? [...]</description>
		<content:encoded><![CDATA[<p>[...] Z-Index And The CSS Stack: Which Element Displays First? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Z-Index And The CSS Stack: Which Element Displays First? &#124; favSHARE.net</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-45373</link>
		<dc:creator>Z-Index And The CSS Stack: Which Element Displays First? &#124; favSHARE.net</dc:creator>
		<pubDate>Fri, 04 Dec 2009 23:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-45373</guid>
		<description>[...] Read the original article [...]</description>
		<content:encoded><![CDATA[<p>[...] Read the original article [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: favSHARE</title>
		<link>http://www.vanseodesign.com/css/css-stack-z-index/comment-page-1/#comment-45372</link>
		<dc:creator>favSHARE</dc:creator>
		<pubDate>Fri, 04 Dec 2009 23:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/?p=1079#comment-45372</guid>
		<description>This article has been shared on &lt;a href=&quot;http://www.favshare.net&quot; rel=&quot;nofollow&quot;&gt;&lt;b&gt;favSHARE.net&lt;/b&gt;&lt;/a&gt;. Go and vote it!</description>
		<content:encoded><![CDATA[<p>This article has been shared on <a href="http://www.favshare.net" rel="nofollow"><b>favSHARE.net</b></a>. Go and vote it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
