Skip to content

Fix: Mobile navigation drawer overlay is pierced by page headings#1822

Open
Shrutiii01 wants to merge 1 commit into
recodehive:mainfrom
Shrutiii01:fix-docs-text-bleed
Open

Fix: Mobile navigation drawer overlay is pierced by page headings#1822
Shrutiii01 wants to merge 1 commit into
recodehive:mainfrom
Shrutiii01:fix-docs-text-bleed

Conversation

@Shrutiii01
Copy link
Copy Markdown

Description

This PR addresses and completely resolves [Bug]: Mobile navigation drawer overlay is pierced by page headings (z-index issue) #1799.

When opening the mobile navigation or sidebar drawer on documentation pages, main markdown article headings and dynamically generated text labels were piercing through the sliding menu panel. This PR enforces a strict stacking priority baseline, completely isolating the responsive menu framework over the document workspace content.


🚀 Key Changes Implemented

1. Enforced Component Stacking Priority (Commit: 6d66c34)

  • Resolved Header Z-Index Bleed: Targeted the global documentation Markdown wrapper layout rules to enforce a baseline layering scale (z-index: 1 !important). This stops relatively positioned headers (h1, h2, h3) from breaking their container boundaries.
  • Maximized Responsive Drawer Priority: Elevated Docusaurus mobile layout drawer containers (.theme-doc-sidebar-container, .menu--responsive) and dynamic module wrapper strings up to a secure stacking context (z-index: 200 !important).
  • Opaque Backdrop Masking: Applied an explicit solid background override using native theme variables (var(--ifm-background-color)) onto the active responsive sliding drawer. This completely blocks out and hides underlying document labels when the drawer is toggled.
  • Layered Backdrop Blur Context: Normalized the dim overlay mask layer context (z-index: 199 !important) to guarantee background content remains unreadable while the menu panel viewport is active.

🔍 Verification & Testing

  • Prristine Commits Verification: Branch split cleanly from the master code baseline to track an isolated, single-commit layout delivery stream.
  • Cross-Viewport Responsiveness Testing: - Tested locally down to Mobile S frame widths (320px) across deep nested documentation paths (/docs/).
    • Verified that dynamic text markers (e.g., Git Cheatsheet header components) are fully masked by the background color block and stay anchored behind the menu panel.

Checklist

  • My code follows the style guidelines of this project
  • This PR contains exactly one isolated commit for clean upstream tracking
  • Tested changes across light and dark system color presets
  • Verified zero layout degradation across standard desktop viewport constraints

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 31, 2026

@Shrutiii01 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added in-review The current changes are in review and would need approval and testing before merging level 1 10 points recode this is label for leaderboard labels May 31, 2026
@github-actions github-actions Bot added this to the recode:launch 3.0 milestone May 31, 2026
@github-actions
Copy link
Copy Markdown

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@github-actions github-actions Bot added Enhacement gssoc26 label gssoc:approved gssoc label level2 gssoc26 label medium gssoc26 label type:docs gssoc label 5pts labels May 31, 2026
@github-actions
Copy link
Copy Markdown

✅ Synchronized metadata from Issue #1799:

  • Labels: level 1, recode, Enhacement, level2, medium, gssoc:approved, type:docs
  • Milestone: recode:launch 3.0

@Karanjot786
Copy link
Copy Markdown

Hey @Shrutiii01! Saw your work on GSSoC 2026.

We are building TermUI, a TypeScript terminal UI framework with React-style hooks and JSX, rendered entirely in the terminal.

We have 55 unassigned GSSoC issues open, including well-scoped bug fixes with clear repro steps. Your TypeScript background transfers directly.

Karanjot, TermUI maintainer

@Adez017 Adez017 changed the title z index fixed #1799 Fix: Mobile navigation drawer overlay is pierced by page headings Jun 1, 2026
@Adez017 Adez017 moved this to In Progress in @recode-web Jun 1, 2026
@Adez017 Adez017 self-requested a review June 1, 2026 05:20
@Adez017
Copy link
Copy Markdown
Member

Adez017 commented Jun 1, 2026

@sanjay-kv lets verify the changes with the vercel CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Enhacement gssoc26 label gssoc:approved gssoc label in-review The current changes are in review and would need approval and testing before merging level 1 10 points level2 gssoc26 label medium gssoc26 label recode this is label for leaderboard type:docs gssoc label 5pts

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants