mandatoryprogrammer / mandatoryprogrammer/CursedChrome
Permissions required?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
Is there a meaningful difference between <all_urls> and "https://*/*", "http://*/*" in how this extension uses things? It would seem to preclude file://, ftp://, and chrome-extension:// URLs, though I believe it can still access its own extension resources.
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 reviewing the extension's declared URL permissions and Chrome extension permission documentation, focusing on the difference between <all_urls> and explicit HTTP/HTTPS patterns. Document the behavior for file://, ftp://, and chrome-extension:// URLs so the permission requirements and any remaining uncertainty are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100