Avatar fallback order should not happen when a URL is broken
Open
Beginner friendly
Nobody has claimed this yet.
has workaround
scope: avatar
waiting for 👍
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
I shouldn't have to provide /broken.jpg just to use the Avatar fallback order. In a situation like a chat room, where there are multiple avatars that don't have a valid avatar URL, the app is constantly trying to fetch /broken.jpg, resultin gin multiple 404 errors. Please allow src to be undefined and will still fallback on the order.
Search keywords:
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 Avatar component and reproduce the case with an undefined src and fallback order. Done means avatars without valid URLs use the fallback order without requesting /broken.jpg or producing repeated 404 errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100