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

Convert to Manifest V3 #136

Merged
merged 20 commits into from
Jun 4, 2024
Merged

Convert to Manifest V3 #136

merged 20 commits into from
Jun 4, 2024

Conversation

ikreymer
Copy link
Member

@ikreymer ikreymer commented Jan 19, 2023

Converts ArchiveWeb.page to work in Manifest V3
Some caveats:

  • Currently, the dev build doesn't load due to CSP restrictions (hopefully this will be allowed at some point at least for unpacked extensions, see: https://bugs.chromium.org/p/chromium/issues/detail?id=1159293)
  • The extension is now served from chrome-extension://<id>/index.html instead of chrome-extension://<id>/replay/index.html as the service worker registration is no longer needed.
  • SW registration removed (unless in embed mode)
  • Added check to uninstall old service worker from ./replay/sw.js as new service worker is served from ./bg.js
  • CSP disabling allows for PDF text extraction + ruffle to work as before.
  • CSP disabling still needed for replay
  • Brave IPFS: Using declarativeNetRequest to override Origin header to allow access to local IPFS node (may need more work) not adding for now, since this is being deprecated Deprecate local node support and ipfs:// scheme brave/brave-browser#37735
  • Fixes Switch to Manifest V3 #131

rename chrome.browserAction -> chrome.action
include ext/bg.js in sw/main.js (addresses #131)

move replay root to ./ from ./replay/
dynamically import sw.js from bg.js, use bg.js as service-worker entrypoint
ipfs: add Origin header overrides via declarative-net-request rules, also add as permission
via brave-ipfs.json rules

bump version to 0.10.0
@ikreymer
Copy link
Member Author

ikreymer commented Jul 6, 2023

This is ready to go, but awaiting implementation of 'strong keep-alive' for chrome.debugger APIs:
https://bugs.chromium.org/p/chromium/issues/detail?id=1423463
https://bugs.chromium.org/p/chromium/issues/detail?id=1418780

@tsemachh
Copy link

tsemachh commented Jan 7, 2024

@ikreymer I think
https://bugs.chromium.org/p/chromium/issues/detail?id=1139096 is mark as fixed
BTW:
We managed to push our extension in the store with Manifest V3 ,
At the time being they asked us to remove some of the code , I did it via patches for now
@protobufjs+inquire+1.1.0.patch
@webrecorder+archivewebpage+0.11.1.patch
Not sure you can do the same since you need the ruffle in the extension.

@ikreymer ikreymer marked this pull request as ready for review June 4, 2024 00:49
@ikreymer ikreymer merged commit ef2adcc into main Jun 4, 2024
3 checks passed
@ikreymer ikreymer deleted the MV3 branch June 4, 2024 01:13
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

Successfully merging this pull request may close these issues.

Switch to Manifest V3
2 participants