dheeraj12347 commented on issue #1417:
URL: https://github.com/apache/cordova-docs/issues/1417#issuecomment-3749569109

   Hi  @GitToTheHub ,
   
   I’ve made significant progress on the sidebar PR, but I’ve hit a roadblock 
in locating the specific source file for the fix. I wanted to give you an 
update on my environment setup and the issue I'm facing:
   
   Environment & Setup: I have successfully set up the local development 
environment on Windows. I’ve installed Node.js (npm), Ruby 3.4, and Bundler. 
Although I encountered some path issues with Gulp (ENOENT errors for the bundle 
command), I’ve bypassed this by running the Jekyll server directly using bundle 
exec jekyll serve. The site is live locally, and I can clearly reproduce the 
bug where "leaf" items like "Security" do not highlight or scroll, while parent 
items like "Data Storage" work perfectly.
   
   The Blocker: I am struggling to find the exact JavaScript file that controls 
the Table of Contents (TOC) behavior. When I search for terms like 
addClass('active') or scroll, I am getting thousands of results from the 
Bootstrap and jQuery library files in the www/static/js/lib folder, which is 
making it very difficult to isolate the custom Cordova logic. I’ve also 
searched for specific keywords like scrollToSideBar but haven't found a match.
   
   Could you point me to the specific file or directory where the custom 
sidebar click-handling and scrolling logic is located? Once I have the right 
file, I can implement the fix to decouple the active state from the "has 
children" check and submit the PR immediately.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to