monkeytypegame / monkeytypegame/monkeytype
Switching between test modes doesn't always restart the test with the new mode
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
No response
Account config
No response
Current Behavior
If you quickly change your test mode twice (e.g., start at time, change to words and then to quote), the test can still be a words test instead of a quotes test.
Expected Behavior
Test should contain a quote, rather than the random words generated in the words mode.
Steps To Reproduce
- Change your mode to
time - Using the test config bar, change your mode to
words - Quickly, change your mode to
quote - Notice how you still have the words from the
wordsmode, rather than a quote
Environment
- OS: Arch Linux
- Browser: Firefox
- Browser Version: 153.0.3
Anything else?
https://github.com/user-attachments/assets/5cc502d1-2031-4d09-925c-e48b50193473
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
Reproduce the rapid time → words → quote sequence using the test config bar, then trace the mode-change and test-restart flow from that UI entry point. Confirm the final test uses quote content rather than the earlier words content, including when changes happen quickly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100