json-schema-org / json-schema-org/website
🐛 Bug: Inconsistent active state between sidebar navigation and content headings on blog pages
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 169
- Forks
- 484
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
Describe the bug
On blog post pages, both content headings and the left sidebar allow in-page navigation.
However, the active/highlighted state becomes inconsistent when navigating between them.
Steps To Reproduce
- Go to one of the JSON Schema blog pages
- Click a content subheading (e.g., "JSON Data Guide") .Here the heading becomes highlighted (blue)
- Click a sidebar item (e.g., "Performance Improvement")
- Page scrolls correctly to the selected section
- Sidebar item does not show an active state
- Previously clicked content heading remains highlighted, even though it is no longer the current section
Expected Behavior
- Only the currently active section should be highlighted
- Sidebar and content headings highlights should stay in sync
- Previous active highlights should be cleared when navigating via sidebar or scroll
Screenshots
Recording
https://github.com/user-attachments/assets/195b69e8-ce19-4218-8810-7b17fc324bcd
Device Information [optional]
- OS:
- Browser:
- version:
Are you working on this issue?
Yes
Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the linked JSON Schema blog page and reproduce navigation between a content subheading and the left sidebar item. Inspect the page's active-section behavior while clicking and scrolling; done means only the current section is highlighted and sidebar and content-heading states remain synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100