“Sticky” content overlaps dropdown menus

“Sticky” content (using the .sticky-top class for example) overlap dropdown menus. This doesn’t make sense, has been raised before (#28569, #28590, #28926) without any explanation, other than a shoot-down about not rearranging the z-index scale because it’s been like that for however long.

Sorry, but having “sticky” content slide over dropdown menus doesn’t make any sense, whatsoever. So what is the actual rationale for leaving it like this and not even considering fixing it?

[martinbean]

@mdo Cool 🙂

I’m currently overriding the z-indexes in my own project to work around this, but wanted to raise it as it does seem to go against expectations. But I can understand it might get complicated with sticky navbars with dropdowns (where the dropdown needs a higher z-index than the sticky navbar) but then sticky content (like in the example above) that should sit underneath. Maybe the z-index hierarchy should go like this (highest to lowest):

1. Dropdowns (always on top of “sticky” elements, be them navbars or content as per my example).
2. Sticky navbars (so they are always above sticky content).
3. Sticky content, such as the sticky sidebar content example.

[mdo]

That’s more than fair, I get that issue. I think sticky content wasn’t on our minds because we were look at is like sticky navigation in the form of navbars and what not. This is definitely a use case we should account for and would require a z-index update in v5. Not sure what we could do about v4 though.