When ExtPay included twice via two content scripts, onPaid callbacks no longer run
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 767
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
This happened to me while I had a content script that ran on every page AND the normal content script that only includes ExtPay on extensionpay.com/*.
Take out "exclude_matches": ["http://localhost/*"],in dev extension and try to pay with dev extension.
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 issue in the dev extension: remove "exclude_matches": ["http://localhost/*"], then pay while both content scripts include ExtPay. Trace how the two inclusions affect onPaid callbacks, and verify that the callbacks run when ExtPay is included twice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- payments
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100