Go home, z-index, you’re high

This is the most excellent commit message. WORLD WAR Z-INDEX: Restoration of sanity to revisions/slider/menu z-index values. The year is 2013. It is a period of DOM unrest. Sliders have hoarded all available z-index, leading to an arms race. What started as a local squabble soon escalated into a global conflict. The flyout menus were…

This is the most excellent commit message.

WORLD WAR Z-INDEX: Restoration of sanity to revisions/slider/menu z-index values.

The year is 2013. It is a period of DOM unrest. Sliders have hoarded all available z-index, leading to an arms race. What started as a local squabble soon escalated into a global conflict. The flyout menus were the first of the collateral damage, trodden underfoot by mighty warring enemies they couldn’t effectively challenge. It was said they were betrayed by one of their own: the z-index-power-hungry non-active currently-hovered submenu, whose z-index-power level was over 9000!

But there is hope. A small band of heroes has emerged. Using their powers of “what were you thinking?” and “chill, no one needs a z-index THAT high”, they have begun to restore order and harmony to the DOM.

Inspired by fat’s post on Medium, I have begun to strip out all those instances of z-index: 500 and z-index: 10000 and give them a little bit of sanity (I mean, what was I thinking? The ranges do not need to be that far apart).

Since I’m using Sass to compile my css, I really like the idea of setting all the z-index values in a single include. At least I know I’m not the only one who gets kinda nuts with z-index. Now to fix it.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related