content-script support allOpeners option
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request
Add an allOpeners configuration option, similar to allFrames.
When some websites pop up a login verification window (such as Google login), the content-script interface should not be displayed, as this may lead users to believe that the plugin could hijack their login information, causing unnecessary concerns.
Is your feature request related to a bug?
none
What are the alternatives?
none
Additional context
none
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 locating the content-script configuration and the existing allFrames option, then trace how the content-script interface is shown in opener or verification windows. Done means an allOpeners option is supported and prevents the interface from appearing in the specified login popups; add or update coverage for that behavior if the relevant tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100