mandatoryprogrammer / mandatoryprogrammer/CursedChrome
Requiring `redirect-hack.html` for redirects makes injecting into existing extensions break this functionality
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
Ideally this entire thing should be able to be injected into an existing extension with no issues. However currently the `redirect-hack.html` file is used to handle redirects (which will not exist when injected into another extension). Should find a way to remove the dependency on this file so it's more portable...
Contributor guide
No contributing guide indexed for this repository
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 inspecting redirect-hack.html and tracing the redirect flow that depends on it. Check how the project is injected into an existing extension, and treat redirects working without that file as the completion criterion. The issue names no test path, so identify the relevant verification approach while tracing the flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100