Menu entries without sub entries should be highlighted and scrolled to

[GitToTheHub]

Bug Report

Problem

What is expected to happen?

When clicking on a documentation the appropriate menu entry should be highlighted and it should be scrolled to this menu entry.

What does actually happen?

Only menu entries with sub entries will be highlighted and scrolled to.

Information

Clicking on Data Storage will highlight the entry and set the scroll position because it had sub entries. Clicking on Security will not highlight it and not set the scroll position, because it has no sub entries. This makes the navigation through the documentation much harder and confuses.

Command or Code

Environment, Platform, Device

Version information

Checklist

• I searched for existing GitHub issues
• I updated all Cordova tooling to most recent version
• I included all the necessary information above

[dheeraj12347]

Hi, @GitToTheHub,

I’m a student and aspiring full‑stack web developer, and I’d like to work on this issue as one of my first contributions to Apache Cordova docs.
I reproduced the behavior on the documentation site: when clicking on a sidebar item that has sub‑entries (for example “Data Storage”), the item is highlighted and scrolled into view, but items without sub‑entries (like “Security”) are not highlighted and the menu does not scroll to them. This makes it harder to see which section is currently active while navigating through the docs.
My plan is:
Locate the JavaScript responsible for handling the docs sidebar navigation, active menu state, and scroll behavior.
Update the click/activation logic so that all menu entries—whether or not they have sub‑entries—receive the active class and are scrolled into view when selected.
Test the change across different documentation pages and viewport sizes to ensure existing behavior for nested sections still works correctly.
From my side, I have built several front‑end projects (portfolio and other themed sites using HTML, CSS, and JavaScript) and I regularly work with Node.js/Express in my own repositories, so I’m comfortable adjusting UI behavior and debugging JavaScript in a production codebase.

If this approach looks good, I’d be happy to take this issue and open a PR.

[GitToTheHub]

Hi @dheeraj12347,

you are free to make PR to fix this.

Regards

[Soham271]

if possible can you plz provide a video or image