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

Conflict with other extensions in Manifest V3 #14

Open
lawnzapper opened this issue May 25, 2021 · 3 comments
Open

Conflict with other extensions in Manifest V3 #14

lawnzapper opened this issue May 25, 2021 · 3 comments
Labels
MV3 Manifest v3

Comments

@lawnzapper
Copy link

Google search terms

Describe the bug

I'm building a Chrome Extension with manifest v3, bundled with ejected CRA and custom webpack config.
Whenever I install it, both unpacked or from the store, some other extensions as Adblock and Http Everywhere crash, and my extension fails to initialize. I found out that my issue was related to @extend-chrome/storage import, so I removed it and used chrome.storage api with no external dependencies.
I'm sorry but I have not time to create a minimal reproduction right now, since I'm full making an official release of the extension I'm working on.
My thoughts are, maybe it's related to the way manifest v3 works now with service workers, or something creates conflict with the use of rxjs and/or chrome-promise.
Don' t worry about to or not to accept the issue since it's not well compiled, I'm just writing to you for the sake of your own library that was easy to use for me. Bye

How do we reproduce?

Expected behavior

Actual behavior

Screenshots

Please complete the following information:

  • Library Version:
  • Operating System:
  • Browser:
  • Node Version:

Additional context

@jacksteamdev jacksteamdev changed the title Conflict with other extensions Conflict with other extensions in Manifest V3 May 25, 2021
@jacksteamdev jacksteamdev added the MV3 Manifest v3 label May 25, 2021
@jacksteamdev
Copy link
Contributor

jacksteamdev commented May 25, 2021

@lawnzapper Thanks for the heads up!

That's really weird stuff, definitely a bug in Chrome MV3, since one extension should never be able to crash other extensions.

I'll take a look soon.

Question

Are you using the unlimitedStorage permission?

@lawnzapper
Copy link
Author

Are you using the unlimitedStorage permission?

No I'm not, just storage.
Were you able to reproduce the bug?

@jacksteamdev
Copy link
Contributor

@lawnzapper No, I wasn't, but if you put a link for a reproduction repo, I can look at it on Tuesday.

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

No branches or pull requests

2 participants