generated from nhcarrigan/template
Fix footer z-index stacking issue #18
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Our footer is experiencing an intermittent stacking order problem where the page body occasionally renders on top of the footer instead of behind it. This happens randomly on page refresh, which suggests a CSS z-index collision or missing layering context.
This feels like a race condition in how the DOM is being painted, and it's definitely creating a confusing user experience when it happens.
What's happening
Acceptance Criteria
Notes for the team
This might be worth checking if there's a z-index war happening elsewhere on the page, or if the footer needs a stacking context established. The randomness on refresh is the real clue here — let's make sure our layering is bulletproof. 💙
I'm a little confused about this issue. The
footerelement with a class ofpage-footerhas az-indexof1000set in thetheme-witch.cssfile. Thus causing it to render above the page body. The wording of the issue is confusing me on what the appropriate behavior should be.