-
Notifications
You must be signed in to change notification settings - Fork 4
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
Migrate Clippings to Manifest v3 #388
Comments
Seems like there will be a grace period before Manifest v2 is deprecated. From the Mozilla Add-ons Community Blog:
|
The |
- Initial implementation - Extension fully functional until background script is terminated
…t termination (part of issue #388)
Auto-incrementing placeholders are incorrectly reset when the background script terminates. This is because the aeClippingSubst library doesn't save the state of those placeholders into extension storage. |
The Clippings menu items for clippings and folders are duplicated every time the background script is restarted. |
every time the background script is restarted (part of issue #388)
…ound script terminates (part of issue #388)
Fixed a regression bug: issue #455 |
Need to verify that backup notifications will still appear, especially the first-time backup notification. |
Verified backup reminder notifications. |
Firefox will be implementing Manifest v3. Unlike Google Chrome, it will support Event Pages which is similar to background pages, except that it won't be persistent - it may terminate after a period of time.
Clippings needs to be modified so that it can handle unplanned termination of the background script. This will involve a massive overhaul of the Dexie-based Clippings backend architecture, as extension pages hold references to the background script (via
browser.extension.getBackgroundPage()
; this should be changed to use WebExtension messaging.More info on Firefox Manifest v3:
The text was updated successfully, but these errors were encountered: