Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pocket popup should use action #280

Open
29edde2e opened this issue Feb 19, 2022 · 0 comments
Open

Pocket popup should use action #280

29edde2e opened this issue Feb 19, 2022 · 0 comments

Comments

@29edde2e
Copy link

Hello Pocket friends, I am curious why the Pocket chrome extension chooses to inject its UI into the page instead of using browserAction (consolidated into action in MV3). The current design presents a great risk to the user as a malicious webpage (or, another extension) can modify the behavior of the Pocket interface. I made a very quick demo that changes the behavior of the "Gear" icon for example. A higher effort version could even expand the interface to include a fake message informing the user that they need to change their password, and they're actually redirected to a phishing site, etc.

The current design is also just generally more buggy and prone to failure, some websites like Bing aggressively purge injected elements so the pocket popup appears to fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant