Injected code can be rejected due to CSP with Firefox
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hey!
When a site has a CSP policy for script-src not including "self", we get this error:
Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src https://report-uri.com https://api.stripe.com https://js.stripe.com https://www.google.com https://www.gstatic.com https://cdnjs.cloudflare.com https://ajax.cloudflare.com https://www.google-analytics.com”). Source: (function() {
var _addEventListener;....
Such a site is report-uri.io.
Vimium works fine nonetheless.
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 reproducing the Firefox CSP error on report-uri.io with Vimium enabled, then trace the injected-code path responsible for the blocked script. Confirm that the fix prevents the CSP rejection while keeping Vimium functional on the affected site.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100