Fix inconsistent visibility and clipping of Slick carousel navigation arrows on mobile
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css, javascript
- Domain
- frontend
Research direction
Locate the DevRel platform page component in the Gatsby codebase and find where the Slick carousel is rendered. Inspect the CSS controlling the navigation arrows' visibility and positioning at mobile breakpoints (e.g., 360px). Verify the fix using browser responsive mode at 360×760px and 314×709px; done when arrows are fully visible and unclipped.
Written by the indexing model from the issue text.
Description
Description
The Slick carousel navigation arrows on the DevRel platform page behave inconsistently on smaller mobile viewports.
During responsive testing, the previous and next navigation arrows are sometimes not visible. When they do appear, they are partially clipped at the edges of the carousel, affecting their visibility and usability.
Page: https://layer5.io/solutions/devrel-platform-for-kubernetes-and-cloud-native-content
Steps to Reproduce
- Visit the DevRel platform page.
- Open browser developer tools and enable responsive design mode.
- Set the viewport to mobile dimensions (e.g., 360px and 314px).
- Locate the image carousel in the DevRel section.
- Observe the previous and next navigation arrows while interacting with the carousel.
Expected Behavior
- Both previous and next navigation arrows should display consistently on mobile viewports.
- The arrows should be fully visible and properly positioned within the carousel boundaries.
- Navigation controls should remain accessible and usable across different screen widths.
- Their positioning should adapt appropriately to smaller viewport sizes.
Actual Behavior
- Navigation arrows are inconsistently displayed and sometimes disappear.
- When visible, the arrows are partially clipped at the carousel boundaries.
- Their positioning does not appear to adapt consistently to smaller mobile viewports.
Environment
- Browser: Firefox
- Testing mode: Responsive Design Mode
- Viewports: 360 × 760px and 314 × 709px
- Device emulation: Samsung Galaxy S10
Screenshots
Screenshots demonstrating the inconsistent visibility and clipping of carousel navigation arrows are attached.
- 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
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
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