Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

BUG: "Here’s What Our Partners Have to Say" and "partnership process >" don't have scrolling (no option and no automatic scrolling)

Open
#1,001 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Open the for-partners page and reproduce the issue in Chrome or Opera GX, checking the “partnership process” and “Here’s What Our Partners Have to Say” sections. Compare their behavior with the “Our past partners” section to identify the relevant frontend entry point. Done means users can access all slides through a visible scroller or automatic scrolling.

Written by the indexing model from the issue text.

Description

bug

🐛 Bug Report

What went wrong? 🤔

When on the for-partners page, "partnership process >" and "Here’s What Our Partners Have to Say" don't have UI scrolling. No way to scroll besides selecting the text and going utmost right to reveal the next slides. (examples shown)

Expected Behavior

"Scroller" option or "Automatic Scroll" like the "Our past partners" does it.

Actual Behavior

No UI for seeing what the other blocks are.

Steps to Reproduce Issue

Go to the for-partners page, in Chrome/Opera GX and you'll notice there is no scroll bar.

Solution

Adding a scroller or just implemented automatic scrolling just like the "Our past partners" part.

I can do it and send a PR (if I'm told what the expected behavior is).

Environment
Operating System

Windows 11

Browser

Chrome/Opera/Opera GX

Screenshots

image
image
image
image

Dominant language
JavaScript
Stars
78
Forks
69
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hackjunction/JunctionApp

All issues in hackjunction/JunctionApp

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.