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.

Sign up for GitHub

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

Jump to bottom

Google requires migration to MV3 #66

Open
LucasHocker opened this issue Jul 1, 2021 · 1 comment
Open

Google requires migration to MV3 #66

LucasHocker opened this issue Jul 1, 2021 · 1 comment
Labels
techdebt Crap no one wants to do, but must

Comments

@LucasHocker
Copy link
Collaborator

MV3 makes massive changes to permissions and background pages get replaced by service workers. This will require a large amount of changes to core injection logic and has a high risk of causing disruption. Google has traditionally taken anywhere from 1 day to 2 weeks to approve an update. With the new requirement to not include any remote code, a bug could mean all PowerUp users are down for 2 weeks.
@LucasHocker LucasHocker added the techdebt Crap no one wants to do, but must label Jul 1, 2021
@LucasHocker
Copy link
Collaborator Author

https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
techdebt Crap no one wants to do, but must
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LucasHocker