[WEB-3271] fix: adjust z-index to prevent overlap issue with version history panel

[anmolsinghbhatia]

Description

This PR resolves a z-index issue where clicking on the page emoji in the header was causing an unintended overlap when the version history panel was open.

Changes:

Updated the z-index from z-20 to z-[16] to properly manage layering and prevent the version history panel from interfering with the emoji picker.

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Screenshots and Media (if applicable)

Before	After

Test Scenarios

• Open the version history panel and click on the page emoji in the header.
• Ensure that the emoji picker appears correctly without being obstructed.
• Verify that other UI elements remain unaffected.

References

[WEB-3271]

Summary by CodeRabbit

• Style
  • Updated z-index styling for the page versions overlay component to adjust its stacking order.

[coderabbitai]

Walkthrough

The pull request involves a minor styling adjustment in the PageVersionsOverlay component, specifically changing the z-index value from 20 to a Tailwind CSS utility class z-[16]. This modification alters the stacking order of the overlay element within the page's visual hierarchy, potentially affecting how the component is layered relative to other elements.

Changes

File	Change Summary
web/core/components/pages/version/root.tsx	Modified z-index from hardcoded 20 to Tailwind CSS z-[16] utility class

Possibly related PRs

• [WEB-2539] fix: update version history overlay z-index #5694: Previously modified z-index of the PageVersionsOverlay component from z-10 to z-20

Suggested reviewers

• sriramveeraghanta
• SatishGandham

Poem

🐰 A z-index dance, so subtle and light,
Layers shifting with Tailwind's might
From twenty to sixteen, a pixel's slight sway
Stacking order finds its new way
Code rabbit hops with design delight! 🎨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ddad176 and 867ad1d.

📒 Files selected for processing (1)

• web/core/components/pages/version/root.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• web/core/components/pages/version/root.tsx

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.