mandatoryprogrammer / mandatoryprogrammer/CursedChrome
Improperly handling lazy loading of content.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
This plugin fails on pages that load some content after landing and fails to process any loading after a 301 or 302. I suspect it is now confused about the origin of the request. We should probably still process requests from domains where we reside - and that are permitted by the CSP of the page or server.
Try to use this plugin to visit Twitter or Facebook. You'll see the issue right away.
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 reproducing the failure with the plugin on Twitter or Facebook, including content loaded after landing and navigation through a 301 or 302. Trace how request origin and the page or server CSP are handled; done means permitted requests from the residing domains are still processed in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100