[UI] Handbook Table of Contents links are clipped on mobile viewports
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, javascript
- Domain
- frontend
Research direction
The payload names no file, so start by finding the Table of Contents component and its styles in the Handbook article layout, then run the site locally on localhost:8001. Open DevTools responsive mode at 375 × 812, expand the TOC, and inspect the "GitHub Organization Membership" link to see where it overflows its container. Done when long TOC links wrap inside the container at that viewport with no clipped text.
Written by the indexing model from the issue text.
Description
Description
On the [Layer5 Community Handbook](https://layer5.io/community/handbook/code-of-conduct), longer Table of Contents (TOC) links are clipped on mobile viewports.
At a screen resolution of 375 × 812px, the "GitHub Organization Membership" link extends beyond the visible container, making part of the text unreadable.
This issue was observed in the local development environment with the TOC expanded.
Steps to Reproduce:
- Open a Community Handbook article.
- Switch to a mobile viewport (375 × 812px).
- Expand the Table of Contents.
- Observe that longer navigation links are cut off.
Expected Behavior
All TOC links should remain fully visible and readable across mobile screen sizes. Longer text should wrap appropriately without overflowing or being clipped by its container.
Screenshots
Screenshot attached showing the clipped "GitHub Organization Membership" link at 375 × 812px.
Environment:
- Host OS: macOS
- Browser: Brave (DevTools responsive mode)
- Viewport: 375 × 812px
- Environment: Local development (
localhost:8001)
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 1.7k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 69
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from layer5io/layer5
-
Fix inconsistent visibility and clipping of Slick carousel navigation arrows on mobilePossibly taken @AP24110011695 claimed this 14 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
layer5io/layer5#8275 · 4 comments ·
Maintainers usually reply within 1 day
-
Fix logo/graphic fitting within its container on mobile viewportsPossibly taken @AP24110011695 claimed this 14 days ago. Openframework/gatsby good first issue help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
layer5io/layer5#8272 · 4 comments ·
Maintainers usually reply within 1 day
-
[UI] Typography token Heading 1 overflows on mobile viewportsPossibly taken @tanav29 claimed this 4 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
layer5io/layer5#8267 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
[UI] Theme Provider Props table overflows on mobile viewportsPossibly taken @SajanBisht claimed this 15 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
layer5io/layer5#8264 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
[Pricing] Plan cards reference non-existent "Free" and "Team" tiersPossibly taken @sameerkrdev claimed this 14 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
layer5io/layer5#8258 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dlq/synthpopcan#58 ·
Maintainers usually reply within 2 days
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fjaeckel/seriesoftubes#376 ·
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day