Solve your z-index issues | z-index and stacking context explained
HTML-код
- Опубликовано: 17 июл 2018
- While it would be handy (at times) for z-index to be a global value, the truth is, it isn't. It's related to its local stacking context, which can be created by a parent with its own z-index value, but also by other properties such as transform, opacity, and many more, which is something most people aren't aware of.
In this video, I look at what CSS stacking context is, both at how it works with z-index, but also why z-index isn't the only CSS property which creates a stacking context, and how problems can arise that you might not expect as you style your pages, with an attempt at not just looking at the theory, but how it can can problems in the real world.
MDN stacking context, with full list of properties which create a new stacking context: developer.mozilla.org/en-US/d...
Codepens:
codepen.io/kevinpowell/pen/Gd...
codepen.io/kevinpowell/pen/bj...
---
I have a newsletter! www.kevinpowell.co/newsletter
New to Sass, or want to step up your game with it? I've got a course just for you: www.kevinpowell.co/learn-sass
---
My Code Editor: VS Code - code.visualstudio.com/
How my browser refreshes when I save: • How to automatically r...
---
Support me on Patreon: / kevinpowell
I'm on some other places on the internet too!
If you'd like a behind the scenes and previews of what's coming up on my RUclips channel, make sure to follow me on Instagram and Twitter.
Instagram: / kevinpowell.co
Twitter: / kevinjpowell
Codepen: codepen.io/kevinpowell/
Github: github.com/kevin-powell
The moment I realised I haven't fully understand z-index, I immediately came to RUclips and typed 'Z-index kevin powell'. That's how much of trust and respect I have for this man.
me too!!🙂
@@joannehughes6082 Wish you will become a senior soon. All the best.
Same
That trust is well placed.
@@centrumsaiyan7623 are u one ?
Kevin, thanks for the explanation of z-index!
P.S. The beginning of the tutorial will have been less confusing if you gave descriptive class names to the boxes (divs) you were stacking. E.g. box-red, box-green, and box-purple will have been easier to keep up with than box-1, box-2, box-3 where we have to try and remember which color was assigned where.
Yeah, looking back at it, I 100% agree
I was struggling with that for 2 hours straight. Really great tutorials and teaching couch, you make the internet more beautiful man
Thank you!!!!!!!!!
I've run into this so many times!
This helped me, i had my modal component inside a child div, and was very confused as to why the modal would appear behind other components! stacking context u got me. thanks kev.
Thanks a lot for this video. i come back to this video again and again. And everytime it is for a new use-case. This time it was for increasing the z-index of scrollbar thumb for a table content. The concept never gets old.
Thank you so much for helping people like me. Although I read the article in MDN about z-index even before I watched the video and I really thought I understood I found out parts that really I didn't understand! So thanks again
Thank you for such detailed description with examples!
Finally, thanks to your video I have understood a problem in my pet project. Thank you, Kevin!
Thank you! Explaining the positioning helped me out big time 😊
I'm in the process of building my own website in which I'd like to eventually use to start my own business. I have no previous experience of using HTML, CSS, or any other form of web coding, so I'm learning everything from scratch as I create the content for my website. I'm looking to create a blog, and I've run into many problems that occur with the z-index, particularly when coding the menu bar. This video has helped me to solve a MAJOR issue with the menu bar. It was an easy-to-understand video and I know have more freedom to build the website that I'm looking to build. Thank you for creating this video.
This video was very informative. Thank you.
well I'm a bit late to the party, but
THANK YOU
literally the best explanation of stacking .
I encourage you to continue focusing on misunderstood concepts li Block Formatin Context
Thank you
Thanks Kevin! Very informative.
Very well explained. Maybe, instead of box-1, box-2, box-3 etc. Try box-red, box-blue, box-orange. I kept going back and forth trying to connect which boxes numbers were which colors. The class names would be more self evident and self explanatory. Thank you for your videos!
Me too
Reason I'm having to switch from this tutorial. 😞
Thanks for your explanations! Helped me alot.
My problem was the stacking context because of positioning an pseudo element *under* the element itself.
Found that decreasing the z-index on a wrapper fixes the problem of the new stacking context:
.wrapper-around-element {
position: relative;
z-index: 0;
}
.element {
position: relative;
z-index: 1;
}
/* Set pseudo element one level down */
.element span::before {
content: "";
position: absolute;
z-index: -1;
background: red;
top: 0;
right: 0;
bottom: 0;
left: 0;
height: 1em;
}
This is great Kevin.
You know you've spent too much time on the internet as an American when hearing 'zed' doesn't faze you anymore lol great vids Kev as always.
I'm trying to make a periodic table.
I have a section which contains the periodic table (18 columns), and each column has some number of elements.When I hover over an element I'd like it's icon to expand, but when I do this it pushes the elements to the right away as it expands, rather than expanding over them. I'm still very confused but I'll try some of these tricks.
Edit: so I realised the pushing happened because of relative positioning, I tried absolute positioning with left offset and it works except for when I do the last column everything goes to the top of the page.
really, this is very helpful video regarding stacking context, and very helpful for beginners like me. very clean understanding after watching this video. Thanks for this video.
Actually position fixed and sticky are creating a new stacking context without the z-index (with the initial value) according to MDN docs.
Great explanation!!
thanks for explaining it so good 👍
Thank you. Helpful for me.
Wow, that really made me understand Z-indexes a lot.
haha I was just reading about this the other day! Great job Kevin!
Thanks 👍
thanks a lot sir, for this awesome video
This is awesome.
What kind of software are you using to do your side by side coding with the viewing window?
Very good example! Thank you! And even as a CSS newb I understood what you were aiming at.
I have 2 problems: When stacking, 1. How do I make text wrap around the stacked item, e.g. an image? Like if your example boxes were bigger and one of them had text inside them?
2. How do I prevent other elements further down on my page from moving up and chiming in on stacking behavior as well?
Finally! the answers
شكرا علي الترجمه ❤
*PRO TIP:* Search about react portal and the concept will help you with modal, popovers and dropdowns with any framework :)
How do translate , rotate, scale , skew work in terms of stacking context now that they aren’t attached to the transform property and are their own properties?
Vraiment interessant, merci !!!
De rien :D
Amazing thank you. This been a problem a couple of times for me haha
I just ran into an issue with this myself. Frustrating when it happens, but it's nice to know what's causing it :)
Awesome video and explanation. I love your videos and teaching style. Say you wanted some other effect on the .about div and needed transform but still wanted it beneath .portfolio. You could give the .about div position: relative and z-index: -1 and that would work also. It would also not impact anything that came after the .about.
Thank you!
Thank you. I had it several times, when I didn' get it why it didn't work as I wanted.
Glad that this helped!
Thank you
Waiting to continue the svg series 😉😉
Soon!
hi master kevin OwO
I'm having trouble understanding why animation-fill-mode ruins my z-indexing, and so far all the articles I read only gives alternative solutions, but they never explain why this is happening or why it's wrong to use z-indexing with animation..
hope you can somehow help me with this
does z-index: unset; remove any stacking context created by another previous ruleset? would it be a good idea to use
.some-container * {z-index: 0;}
to enforce strict stacking and then
z-index: unset;
to grant rogue permissions to children?
That would be cool, but sadly there is no way to escape a stacking context. Unset would just reset that z-index to the default.... which I'm guessing is 0.
hmm, ok, thanks 🙂
Thank you! really!
thank you
Great video. Took me a couple of watches to truly get it, but I think part of that was that I found the basic idea hard to get my head around. Just one question, on the final example, if you had kept the transform on the about section, could you have used a negative z-index value to bring it behind the portfolio items, or is the z-index only going to work if the it's has a non-default position property set?
Try to understand that the most important thing here is the stacking context. Followed by z-index.
z-index is all but value for comparison.
case 1: if a and b are siblings
a(z-index)= 1000 b(z-index) = 1 then a> b similarly if a(z-index)= 1 and b(z-index)= -1000 then too a>b
case 2: if a and b are siblings and c is a child of b and a has a higher z-index than b. the the value of z-index of c is futile.
I just tested one of my theories using the CodePen that Kevin shared in the video description, and it worked. To get the negative z-index to work on the about section, whilst still using the transform, you just have to set position to 'relative'. That way the stacking context for the about section can be positioned behind the figures.
As you tested (always a great way to learn!), It works 😁. As you mentioned, it's moving that below the other section, so it's stacking context is still unique, but it's all below the others. Always more than one way to solve these things with CSS
@@devmrin unless b doesn't have a stacking context, then essentially a and c will become siblings in their parent stacking context.
im just confused because in this video applying z-index:1000 puts box-5 back on top but if you look at the codepen , that's not working ..box-6 is still on top .
if you add position:relative to box-5 that puts it back on top but just saying the way you have it in the video is not working...so , this video is a year old so im not sure if something changed in the way stacking context works or what...
Yes, very strange. I don't know how that worked without positioning the box... A possible explanation is that Codepen didn't save the opacity of .5 on .box-6, it got stuck on 1. Weird that Kevin didn't notice that. :D Nonetheless, good work by Kevin.
Welcome back Kevin and thanks for clarifying to me the Z-index just a question about something else, what code do you use or how do you bring the node command line into your VS code terminal text editor just as you did it when building the portfolio project? you were not switching in and out of VS code but watched everything in the VS code the terminal
You can use VS Code's built in terminal - just hit (control) + (~) together. Or alternatively search for Toggle Integrated terminal in the menu on the top.
Thanks for your concern M.Mukherjee, in fact I'm asking for ways to use things like gulp from the VS code terminal than switching in and out of VS code,
As Mrinmay mentioned control + ~ will open the terminal, and then you can keep working like you would in a seperate terminal, using gulp or anything else you'd like.
Thanks, I kind of a fan of z-index.
No problem 👍
Thanks!
Thank you so much (and sorry for missing this until now!)
Great explanations thank you !!! But position fixed creates a stacking context without the need of a z-index value (unlike position relative) ;) 06:25
i think i found out why we need to use the scale value other than 1 in order to create a new stack. Because 1 is default. Browser's engine looks at your code sees "scale(1)" and does nothing because it is already 1 . But if the engine sees .9 (or something other than 1) it pull out the node apply scale over that node put it back so this creates a new stack. What do you think ? i am right?
At 7:31 the scale(1) does create a new stacking context...
sorry my bad. I meant to talk about "opacity:1". scale (1) does create a new context because initially, transform object is undefined. If you define a transform namely "scale (1)" which is not default. It also defines a new context
I only say 'zed' when referring to the ZX Spectrum👌.
It is also working,
Please guide me if this is the wrong way.
.about {
background: var(--clr-accent);
position: relative;
z-index:-500;
transform: translateY(-10em);
padding: 10em 5em 5em;
}
Really stuck with the stacking context and pseudo elements when making a .card item with a banner that looks like it wraps behind and to the left
I know you've made a tutorial on it, but I can't for the life of me find it. It's a shame chrome dev tools can't make the context more obvious
Very valuable! Thanks!
For better understanding you should have used the class name of the boxes based on the color of it.
6:14 renaming the classes as .box-one -> .box-red, .box-two-> .box-green, .box-three-> .box-purple, would make it easier to reason about the code :)
Waiting to get to the part where you actually explain what a stacking context is. I'm at 8:45. You keep talking about it, but have yet to explain what it is :| I may have missed it?
It finally all came together at the end though. A stacking context is like a tree. Anytime you apply a z-index to a element, the element gets inserted into the tree. Its position in the tree is as a child of the closest stacking context containing element in the dom ancestors. Sort of the same way that when you absolutely position an element, its position is relative to the closest positioned ancestor element in the dom. So now this z-indexed element (element A) will interact with other children of the stacking context it belongs to, but, since applying a z-index creates a stacking context for element A, any descendants of the element A will be relative to the its stacking context as its own flattened layering system. Meaning element A's siblings in its containing stacking context cannot get in between the descendants of element A. If you wanted to do that you'd have to remove any css properties that gives element A a stacking context (like the z-index property) and now all the descendants will be in the same context element A used to be in and are free to shuffle around with the siblings in that stacking context.
Sorry it took so long to get there! I felt that I needed the preamble to properly explain it.
Holy Crap! I feel like an idiot now, never knew this
Hello Sir, In code above I want to place leftButton1 and rightButton1 on left and right corner with background transparent and images should be below these two. Also, I do not want to use absolute positioning. How it will be done?
Funtastic
chrome doesn't honor the "z-index: 1000" on box-5. firefox works fine though
can you make bootstrap 4 tutorial???
I've made one site with Bootstrap 4, though at the time it was in beta so things changed a little since. I probably won't be looking at it again
Should of given the class names the color of the box instead of a random name
You saved my life😄
2:38
oh yes i agree!!
This video would have been easier to understand if instead of box one, box two , box three . The box-colors would have been used.
M making a search engine for my project by jquery filter function but I want the searched keywrod to be highlighted with the content ex: if i search 'asp' it wil come aspirin but i wnt more in that asp should be highlighted
Highlighted over other possible options?
Kevin Powell no highlight over the input from the content
one mistake you did insted using number id u need to use there name red green ....
What's wrong with using numbers? It's just a demo, I wouldn't use names like this on a real project (or even go with red, green, etc either as the color could change!)
Definitely zed
le problème c'est qu'il y a deux difficultés : comprendre le stacking context et comprendre....la voix anglaise.
{2024-05-15}
Z index is pain
z-index used with transform should not affect the stacking order.
Man, you should have referred to them as 'purple box' / 'green box' etc... You would have avoided sentences like 'box 1 has index of 2 and 2 has index of 1'...
That would have been much smarter of me :\
well it’s hard to think of all details when you are actually doing the hard job recording a video :) but it’s still amazingly well explained!
"zed" is proper English.
Tomato, tomaato; z, zede, Canada, US Minor