Word replay text colour contrast is hard to see

Open
#8,252 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
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Reproduce the typing test with the Rainbow Trail colour theme and compare the appearance of typed and previewed letters. Locate the frontend styling or theme entry point that controls these colours, then verify the contrast is clearly distinguishable for both states while typing.

Written by the indexing model from the issue text.

Description

bug
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

To the devs and mods of Monkeytype,

Image

https://github.com/user-attachments/assets/6a6b0127-3cea-4d10-82c5-127a336869d0

As you can see, (barely) the text after the 'o' in 'one' is not typed yet (previewed). It's pretty hard to see the colour difference, even after sitting right in front of the screen. Some people might have eyesight issues, which makes this problem worse for them.

Basically, it's hard to see which letters/words are typed and not typed.

Please note that this issue only occurs in the Rainbow Trail colour theme.

Thank you for your time,
Kauman151

Account config

No response

Current Behavior

No response

Expected Behavior

No response

Steps To Reproduce

No response

Environment
  • OS:
  • Browser:
  • Browser Version:
Anything else?

No response

Dominant language
TypeScript
Stars
20.7k
Forks
3.3k
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 monkeytypegame/monkeytype

All issues in monkeytypegame/monkeytype

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.