Skip to content

Conversation

@Sourya07
Copy link
Contributor

Description

This PR fixes #2530

Notes for Reviewers

Signed commits

  • Yes, I signed my commits.

@netlify
Copy link

netlify bot commented Jan 11, 2026

Deploy Preview for mesheryio-preview ready!

Name Link
🔨 Latest commit de29297
🔍 Latest deploy log https://app.netlify.com/projects/mesheryio-preview/deploys/69637493bdf06a0008761d03
😎 Deploy Preview https://deploy-preview-2533--mesheryio-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Sourya07, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue where multiple navigation dropdowns could remain open simultaneously, leading to a suboptimal user interface. The core change updates the navbar's JavaScript functionality to manage dropdown states, ensuring that opening one dropdown automatically closes any others that are currently open. This enhancement significantly improves the user experience by maintaining a clean and intuitive navigation flow. Additionally, some minor cosmetic adjustments were made to the recognition page.

Highlights

  • Navbar Dropdown Behavior: Implemented a fix to ensure only one dropdown menu in the navbar remains open at a time, preventing multiple menus from overlapping and improving user experience.
  • JavaScript Logic Refinement: Refactored the navbarExpand JavaScript function to automatically close sibling dropdowns when a new one is activated, streamlining navigation interaction.
  • Content Styling Updates: Applied minor styling and structural updates to the recognition.md page for improved presentation and consistency.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully fixes an issue where multiple navigation dropdowns could be open at the same time. The logic added to js/stellarnav.js correctly closes other open dropdowns before opening a new one, which is a solid implementation.

The PR also includes several formatting and style improvements in collections/_pages/recognition.md and js/stellarnav.js. While most of these are beneficial, I've pointed out one instance in the markdown file where using inline styles could be improved for better maintainability by moving them to a separate CSS file.

Overall, the core issue is well-addressed, and the other changes are mostly positive.

Comment on lines 34 to 37
<ul style="padding-left: 20px; text-align: left;">
<li style="margin-bottom: 2rem;"><em><a href="https://badges.layer5.io">Layer5</a></em> - Badges are one of the many ways that we recognize the efforts of our contributors and uplift our users. Badges represent milestones that you achieve both in using and in contributing to Meshery. As a contributor, this is how you demonstrate your ownership, dedication, skills and commitment. As a user, this is how you demonstrate your prowess, milestones, and meaningful engagement.</li>
<li><em><a href="https://github.com/meshery/meshery.io/pulls">Add your program here</a></em> - Add your recognition program to this list by <a href="https://github.com/meshery/meshery.io/pulls">submitting a pull request</a>.</li>
</ul>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this change achieves the desired styling, using inline styles in HTML is generally discouraged as it mixes content with presentation, making the code harder to maintain. A better approach is to use CSS classes.

Please consider moving the styling to a CSS file and applying it with classes. You would then need to add the corresponding styles for these classes in your project's stylesheet.

For example:

.recognition-list {
  padding-left: 20px;
  text-align: left;
}

.recognition-item-spaced {
  margin-bottom: 2rem;
}
Suggested change
<ul style="padding-left: 20px; text-align: left;">
<li style="margin-bottom: 2rem;"><em><a href="https://badges.layer5.io">Layer5</a></em> - Badges are one of the many ways that we recognize the efforts of our contributors and uplift our users. Badges represent milestones that you achieve both in using and in contributing to Meshery. As a contributor, this is how you demonstrate your ownership, dedication, skills and commitment. As a user, this is how you demonstrate your prowess, milestones, and meaningful engagement.</li>
<li><em><a href="https://github.com/meshery/meshery.io/pulls">Add your program here</a></em> - Add your recognition program to this list by <a href="https://github.com/meshery/meshery.io/pulls">submitting a pull request</a>.</li>
</ul>
<ul class="recognition-list">
<li class="recognition-item-spaced"><em><a href="https://badges.layer5.io">Layer5</a></em> - Badges are one of the many ways that we recognize the efforts of our contributors and uplift our users. Badges represent milestones that you achieve both in using and in contributing to Meshery. As a contributor, this is how you demonstrate your ownership, dedication, skills and commitment. As a user, this is how you demonstrate your prowess, milestones, and meaningful engagement.</li>
<li><em><a href="https://github.com/meshery/meshery.io/pulls">Add your program here</a></em> - Add your recognition program to this list by <a href="https://github.com/meshery/meshery.io/pulls">submitting a pull request</a>.</li>
</ul>

@Sourya07 Sourya07 force-pushed the fix-nav-dropdown-overlap branch from 7bae5be to de29297 Compare January 11, 2026 09:59
@Sourya07
Copy link
Contributor Author

formatting issue 😩

@Sourya07
Copy link
Contributor Author

Sourya07 commented Jan 12, 2026

@CodexRaunak
@saurabhraghuvanshii
do we have comands in the meshery.io for auto formatting ?

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Multiple dropdowns remain open simultaneously in navbar

1 participant