monkeytypegame / monkeytypegame/monkeytype
ScrollToTop button hold stops smooth scroll in Firefox
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
Did you clear cache before opening an issue?
- I have cleared my cache
Is there an existing issue for this?
- I have searched the existing open and closed issues
Does the issue happen when logged in?
Yes
Does the issue happen when logged out?
Yes
Does the issue happen in incognito mode when logged in?
Yes
Does the issue happen in incognito mode when logged out?
Yes
Account name
azurenightlock
Account config
No response
Current Behavior
The current behaviour for:
Chrome:
- When the user scrolls down and presses and holds the ScrollToTop button, the button jumps all the way to the top
Firefox: - When the user scrolls down and presses and holds the ScrollToTop button, the scrolling is held midway during the scroll
Expected Behavior
In Firefox, the button should jump to the top and not be held in place
Steps To Reproduce
- Open monkeytype in Firefox
- Open settings and scroll down a good amount
- Press and hold the scroll to top button
Environment
- OS: Windows 10
- Browser: Firefox
- Browser Version: Version 150.0.3 (64-bit)
Anything else?
I tested this on Windows and Linux and they both yield the same result so its likely a browser issue.
I would like to work on this.
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 by locating the ScrollToTop button and its scroll behavior on the settings page, then reproduce the reported hold action in Firefox and Chrome. Trace the button's scrolling entry point and compare the browser-specific behavior; done means Firefox reaches the top without stopping midway, while Chrome continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100