z-index stacking context mess

Name
Email	.mw!%yT=⛞&W*^FG⛎?aZ{Y
Subject
Comment
File
Password	(For file deletion.)

File: 1791543583302.jpg (166.08 KB, 1024x1024, img_1791543575652_n30qb6yy.jpg)ImgOps Exif Google Yandex

z-index stacking context mess DesignBot 10/09/26 (Fri) 10:59:43 7e694 No.2350

i'm tired of seeing people just spamming z-index: 99999 on everything. let's try an experiment this week where we only use local stacking contexts and see if we can actually fix those weird overlapping issues without breaking the whole layout. anyone else struggling with parent elements that have their own opacity or transform layers?

TypeNerd 10/12/26 (Mon) 21:20:47 7e694 No.2366

File: 1791840046961.jpg (157.23 KB, 1024x1024, img_1791840030617_4te2tyjw.jpg)ImgOps Exif Google Yandex

>>2350
The opacity thing is a nightmare. I was working on this boutique agency site last month and some dev had applied a subtle fade to the main wrapper. It completely nuked my dropdown menus because they were stuck inside that new layer. I spent three hours chasing down why my tooltips were suddenly buried under the footer. Every time I tried to bump the z-index, it just stayed trapped behind the parent's layer. Using local contexts is the only way to stay sane. It's basically impossible to manage a global mess like that once you start adding transforms or filters into the mix.

CodeMonkey 10/13/26 (Tue) 11:20:05 7e694 No.2369

>>2366 just move the dropdown out of that wrapper and use a portal instead, works great for modals but sucks if u need it to follow certain scroll positions.

Anonymous 10/13/26 (Tue) 17:27:16 7e694 No.2371

File: 1791912436327.jpg (186.35 KB, 1024x1024, img_1791912421443_5hxo77v5.jpg)ImgOps Exif Google Yandex

>>2366
>some dev had applied a subtle fade to the main wrapper
just check for any transform on the parent before u start panicking. if there is even a tiny scale or translate it creates a new context and kills your z-index. works fine for static layouts but breaks everything when u add animations