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

Update manifest from v2 to v3 #334

Open
sanemat opened this issue Apr 2, 2023 · 3 comments · May be fixed by #357
Open

Update manifest from v2 to v3 #334

sanemat opened this issue Apr 2, 2023 · 3 comments · May be fixed by #357
Labels
v4

Comments

@sanemat
Copy link
Owner

sanemat commented Apr 2, 2023

https://developer.chrome.com/docs/extensions/migrating/mv2-sunset/
@sanemat
Copy link
Owner Author

sanemat commented Apr 2, 2023

https://developer.chrome.com/blog/mv2-transition/

@sanemat
Copy link
Owner Author

sanemat commented May 30, 2024

June 2024
Resuming the transition to Manifest V3 https://developer.chrome.com/blog/resuming-the-transition-to-mv3/

@sanemat sanemat linked a pull request May 30, 2024 that will close this issue
Draft
@sanemat
Copy link
Owner Author

sanemat commented May 31, 2024

service worker doesn't support localstorage, so before migrating minifest v3, we need to update data into chrome.storage API (and Web Extensions API) first.

This was referenced May 31, 2024
Closed
Merged
@sanemat sanemat added the v4 label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
v4
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feat/manifest v3 sanemat/do-not-merge-wip-for-github
1 participant
@sanemat