CSS: The Definitive Guide, 3rd Edition (51 page)

With all of the positioning going on, there will
inevitably be a situation where two elements try to exist in the same place,
visually speaking. Obviously, one of them will have to overlap the other—but how
does one control which element comes out "on top"? This is where the property
z-index
comes in.

z-index
lets you alter the way in which
elements overlap one another. It takes its name from the coordinate system in
which left-to-right is the
x
-axis and top-to-bottom is the
y
-axis. In such a case, the third axis—that which runs
from front to back, or if you prefer, away from the user—is termed the
z
-axis. Thus, elements are given values along this axis and
represented using
z-index
.
Figure 10-52
illustrates this
system.

Figure 10-52. A conceptual view of z-index stacking

In this coordinate system, an element with a high
z-index
value is closer to the reader than those with
lower
z-index
values. This will cause the
high-value element to overlap the others, as illustrated in
Figure 10-53
, which is a "head-on" view
of
Figure 10-52
. This is referred to
as
stacking
.

Figure 10-53. How the elements are stacked

Any integer can be used as a value for
z-index
, including negative numbers. Assigning an element a negative
z-index
will move it further away from the
reader; that is, it will be moved lower in the stack. Consider the following
styles, illustrated in
Figure
10-54
:

p#first {position: absolute; top: 0; left: 0;
width: 20%; height: 10em; z-index: 8;}
p#second {position: absolute; top: 0; left: 10%;
width: 30%; height: 5em; z-index: 4;}
p#third {position: absolute; top: 15%; left: 5%;
width: 15%; height: 10em; z-index: 1;}
p#fourth {position: absolute; top: 10%; left: 15%;
width: 40%; height: 10em; z-index: 0;}

Figure 10-54. Stacked elements can overlap each other

Each of the elements is positioned according to its styles, but the
usual order of stacking is altered by the
z-index
values. Assuming the paragraphs were in numeric order, a
reasonable stacking order would have been, from lowest to highest,
p#first
,
p#second
,
p#third
,
p#fourth
. This would have put
p#first
behind the other three elements and
p#fourth
in front of the others. Now, thanks to
z-index
, the stacking order is under your
control.

As the previous example demonstrates, there is no particular
need for the
z-index
values to be contiguous.
You can assign any integer of any size. If you want to be fairly certain that an
element stayed in front of everything else, you might use a rule such as
z-index
:
100000
.
This would work as expected in most cases—although if you ever declared another
element's
z-index
to be
100001
(or higher), it would appear in
front.

Once you assign an element a value for
z-index
(other than
auto
), that
element establishes its own local
stacking context
. This
means that all of the element's descendants have their own stacking order,
relative to the ancestor element. This is very similar to the way that elements
establish new containing blocks. Given the following styles, you would see
something like
Figure
10-55
:

p {border: 1px solid; background: #DDD; margin: 0;}
b {background: #808080;}
em {background: #BBB;}
#one {position: absolute; top: 0; left: 0; width: 50%; height: 10em;
z-index: 10;}
#two {position: absolute; top: 5em; left: 25%; width: 50%; height: 10em;
z-index: 7;}
#three {position: absolute; top: 11em; left: 0; width: 50%; height: 10em;
z-index: 1;}
#one b {position: absolute; right: -5em; top: 4em; width: 20em;
z-index: -404;}
#two b {position: absolute; right: -3em; top: auto;
z-index: 36;}
#two em {position: absolute; bottom: -0.75em; left: 7em; right: -2em;
z-index: -42;}
#three b {position: absolute; left: 3em; top: 3.5em; width: 25em;
z-index: 23;}

Figure 10-55. Positioned elements establish local stacking contexts

Note where the
b
and
em
elements fall in the stacking order. Each of them
is correctly positioned with respect to its parent element, of course. However,
pay close attention to the children of
p#two
.
While the
b
element is in front of its parent,
and the
em
is behind, both of them are in front
of
p#three
! This is because the
z-index
values of
36
and
-42
are relative to
p#two
but not to the document in general. In a sense,
p#two
and all of its children share a
z-index
of
7
, while having their own mini-
z-index
within the context of
p#two
.

Put another way, it's as though the
b
element has a
z-index
of
7,36
while the
em
's value is
7,-42
. These are merely implied conceptual values; they don't conform
to anything in the specification. However, such a system helps to illustrate how
the overall stacking order is determined.
Consider:

p#one        10
p#one b      10,-404
p#two b      7,36
p#two        7
p#two em     7,-42
p#three b    1,23
p#three      1

This
conceptual framework precisely describes the order in which these elements would
be stacked. While the descendants of an element can be above or below that element
in the stacking order, they are all grouped together with their
ancestor.

It is also the case that an element that establishes a
stacking context for its descendants is placed at the
0
position of that context's
z
-axis. Thus, you
could extend the framework as
follows:

p#one        10,0
p#one b      10,-404
p#two b      7,36
p#two        7,0
p#two em     7,-42
p#three b    1,23
p#three      1,0

There
remains one more value to examine. The specification has this to say about the
default value,
auto
:

Thus, any element with
z-index
:
auto
can be treated as though it is set to
z-index
:
0
. Now, however, you may wonder what happens to elements with a
negative
z-index
value that are part of the
initial containing block's stacking context. For example, ask yourself what should
happen given the
following:

Where am I?


        	
			  
        	

Given
the rules of stacking, the
body
element should
be at the same stacking context as its parent's box, so that would be
0
. It does not establish a new stacking context, so
the absolutely positioned
p
element is placed
in the same stacking context as the
body
element (that of the initial containing block). In other words, the paragraph is
placed
behind
the
body
element. If the
body
has a nontransparent
background, the paragraph will disappear.

That was a possible result
in CSS2, at any rate. In CSS2.1, the stacking rules have been changed so that an
element can never be stacked below the background of its stacking context. In
other words, consider the case where the
body
element establishes a containing block for its descendants (if it were relatively
positioned, for example). An absolutely positioned element that is descended from
the
body
element can never be stacked below the
body
's background, although it can be
stacked below the
body
's
content.

As of this writing, Mozilla and related browsers completely
hide the paragraph even if you set both the
body
and
html
elements to have
transparent backgrounds. This happens in error. Other user agents, like Internet
Explorer, place the paragraph above the
body
's
background even if it has one. According to CSS2.1, that's the correct behavior.
The upshot is that negative
z-index
values can
lead to unpredictable results, so use them with caution.

Figure 10-56. Emulating frames with fixed positioning

Figure 10-57. Separating the "frames" with margins

You can also read about emulating fixed positioning in older versions of IE/Win
at
http://css-discuss.incutio.com/?page=EmulatingFixedPositoning
.
^[
*
]