ProtonMail / ProtonMail/WebClients
[Bug] `5.0.113.4 β` utilises dynamic hotlinking for `img`s which do not support it, thereby rendering them 404.
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have searched open and closed issues for duplicates
- This isn't a feature request
- This is not a report about my app not working as expected
Problem
trakt/trakt-web/issues/2233#issuecomment-4399215226 explains.
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 reading the linked Trakt issue explanation and locating the dynamic hotlinking path for img elements in the TypeScript web clients. Confirm which unsupported images produce 404 responses and trace the affected frontend entry point. Done means those images no longer resolve through unsupported dynamic hotlinking and no longer render as 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100