Ready to watch this entire course?
Become a member and get unlimited access to the entire skills library of over 4,800 courses, including more Web and personalized recommendations.Start Your Free Trial Now
- View Offline
- Reviewing the box model
- Calculating em and percentage values
- Controlling how elements display
- Creating fixed, fluid, and responsive layouts
- Structuring content with HTML5
- Floating elements
- Using relative, absolute, or fixed positioning
- Defining column spacing
- Creating grid-based assets and layouts
- Considering mobile-design-specific issues
- Working with multi-column text
- Enhancing page design CSS Sprites
Skill Level Beginner
You may have noticed in several of our exercises so far that positioning elements can often result in them overlapping each other. To make sure that your layouts behave the way that you expect them to, you need to understand the rules that govern the stacking of these elements and how you can control stacking through CSS. So I have the stacking.htm file open, and there are a few changes. For the most part it's the same, but we have some text now that describes Z-index, which is the property that we are going to be controlling, and then we have our containing element and the three div tags inside of it, so that much is the same.
But currently, now, all three of those elements have been positioned using absolute positioning. And if I preview the file in a browser, you can see these three elements are stacking one right on top of the other because their offsets aren't far enough to keep them from overlapping. So notice that by default right now we are not controlling the stacking in anyway. Notice that by default, they are overlapping one on top of the other, and what's controlling the order of the stacking right now is the source order of the code.
So the last object encountered in the code, the last one rendered, is stacked on top of the other objects. You can think of them as sort of like the first one will be on the bottom, then the second, and then the third. In fact, if we change that source order, so if I go down here to our elements and if I take the first element here, and I am just going to cut that out and then move it down here below the third one, now it's not going to change their position in the layout at all, because they're being absolutely positioned. What it does change, however, is the order in which they're encountered by the browser in the code.
So now, if I save that and go back into the browser and refresh, you can see that now One is actually on top of Two. It would be on top of Three actually as well, if they were overlapping, because now One is encountered last, so it is the topmost object. All right, I am going to undo that because I want us to work from the context of sort of the default one as we begin to control it. Now if we want to take control of the stacking process, the property that we use id does the Z-index properties.
You can think of Z-index, like, you have an X axis and a Y axis that control horizontal and vertical positioning. You can think of the Z axis as controlling stacking, and Z-index allows us to tell an element where it fits along that Z axis, if you will. All right, so I am going to go to element 1, and I am just going to do Z-index. That's the name of the property, z- index, z-index, and I am going to go ahead and give it an order of one, or a value of 1, I should say.
For element 2, I am going to give a z-index of 3, and for element 3 I am going to give it a z-index of 2. Now I am doing these in one-value increments, one, two, and three. The actual value doesn't matter; what matters is which value is higher. The higher the value, the higher it is in the stacking order. So I could have put element two at 400 and it wouldn't have mattered; it would still be on top of those other two. So how far away you space them in values is totally up to you, and is usually dependent upon how many objects you have stacking and how much control you need.
So if I save this, go back to the browser and refresh, boom, you can see that now element number Two is on top because it has the highest z-index value. If I go back into the code, let's see what happens if two elements have exactly the same z-index value. So, if I go to element1 and give it a z-index of 3 and leave element 2's z-index of 3, so if I save that and preview it, you can see that it doesn't appear like anything else has happened, but what's actually happening here is to resolve the conflict between One and Two who have the same z-index value, source orders is then used, so it falls back source order and since Two comes after One, Two wins the battle, even though the two of them have exactly the same z-index.
You can use negative values. If I go into element1 and change its z-index from 3 to -1, if I save this and go back to my browser, let's take a look at what happens. So that actually moves it down below elements that are considered in normal document flow. I mean one of the ways that I like to describe this to people is think about a piece of paper, just being two- dimensional, flat. All of your elements in normal document flow are kind of painted on the flat canvas. And then if you position elements using positioning, it pretty much takes them off of that flat canvas.
It sort of hovers them, if you will, over the page. Well, negative values send it below the page. But what you have to understand is it's going to send it below everything except for what it calls the initial stacking context, which is really fancy and will impress people at the cocktail parties if you use that term. So our HTML tag, or this gray background back here, is the initial stacking context. It's the first element, so it establishes the initial stacking order. So negative values will move it below everything except for that initial stacking context, which is why it's below the body, this white box here, but not below the HTML tag, which is the gray box.
Stacking contexts are another thing that you really need to understand, and it's not the easiest thing in the world to understand. Every element, once that element is given a z-index rating, it establishes a new stacking context. So initially the only stacking context you have on the page is the initial root tag, which is the HTML element. But once you apply a z-index rating to an element, that element begins a new stacking context. Now, if it contains child elements, they are now all considered part of that one stacking context, which is different.
It's easier to see than it is to sort of understand it the first time you hear, so let me show you. So we know that our div tags are wrapped in this section, so that section, you can think of that as a containing element. So if go up to my container selector and I add a z-index value here of 1 and save that, if I go back in the browser and refresh, watch what happens to the number One. All of a sudden, even though it has a negative value, it comes up.
Now it is still the bottom of our stacking order here, but the reason that it comes up is that now it belongs to the stacking context of the containing element, which is this sort of brown background here. So it no longer belongs to the stacking context of the HTML tag; it belongs to the stacking context of the container section, which means that now it's going to order itself based on that context. So now that we have seen this a little bit, let's go through this list that we have right here in the browser that talks about the rules behind stacking context and how stacking conflicts are resolved.
So the first the first bullet point and the very first thing you see here is that the backgrounds and borders of the element forming the stacking context is painted first. In this case, you can think of it as the gray background to the browser window. And then next, any child-stacked elements with a negatives z-index. Now that would have been our element number 1, but it's in a new stacking context now. Next after that, elements in normal document flow. That will be the body, all the text that you see on the page, that sort of thing. Then any non-positioned floats, so floated elements do hover over elements in normal flow, but they're not quite as high as elements that are positioned with z-index.
After that, it would paint any child- stacked elements with z- index of zero or auto. So if you position something, if you say, position absolute, for example, or position fixed, and you don't give it a z-index rating, the z-index is considered to be zero or auto. And then right after that, any child-stacked elements with a positive z- index value, lowest to highest. So that's how stacking order is determined as the page is being painted within the browsers. Now, in most cases you are not going to need to go into it that deep.
Most of the time the default stacking orders are going to work just fine, but every now and then you are going to find yourself needing to tweak your layouts and use z-index property. Now it's especially true if you're working with heavily positioned layouts or for when you're building complex widgets or interface components, things like that. Now in those cases, understanding how stacking context and the z-index property, understanding how those work, can be extremely important.
Sign up for a Premium Membership to download courses for Internet-free viewing.
Watch offline with your iOS, Android, or desktop app.Start Your Free Trial
After signing up, download the course here or from the iOS/Android App.