如何用JavaScript永久删除Firefox扩展Storage Sync中的记录？

Great question—this is a common gotcha when working with Firefox's sync storage, and it ties into how the browser's sync engine is designed under the hood.

Let’s break this down clearly:

Why browser.storage.sync.remove() Doesn’t Physically Delete Records #

Firefox’s storage.sync uses a sync-first architecture. When you call remove(), it doesn’t immediately delete the record from the storage-sync.sqlite file—instead, it marks the record with _status: "deleted". This is intentional:

• The sync engine needs to propagate the deletion to all devices logged into the same Firefox account.
• Marking records as deleted ensures that even if a device is offline when the deletion happens, it’ll catch up once it reconnects.

Can You Permanently Delete Records via Extension JS? #

Short answer: No, you can’t directly force physical deletion of records from the underlying SQLite file using extension JavaScript. Here’s why:

• Extensions run in a sandboxed environment and have no access to the browser’s local file system (including storage-sync.sqlite).
• The browser.storage.sync API abstracts away low-level storage details—its purpose is to handle sync logic, not direct file manipulation.

What You Need to Know #

Even though the record remains in the SQLite file temporarily, from your extension’s perspective, the data is gone:

• Calls to browser.storage.sync.get() will automatically filter out records marked as deleted, so you’ll never retrieve them via the API.
• Firefox’s sync engine will eventually clean up these marked-for-deletion records automatically—this usually happens during regular sync cycles, or when the browser needs to free up storage space.

Workarounds for Testing/Manual Cleanup #

If you need to fully wipe sync storage for testing purposes (not via your extension code):

• Manually close Firefox, locate and delete the storage-sync.sqlite file in your Firefox profile directory.
• Use browser.storage.sync.clear() to mark all sync records as deleted—again, this doesn’t physically remove them immediately, but it ensures no data is accessible via the API.

Remember: For your extension’s core functionality, relying on browser.storage.sync.remove() is the correct approach. The underlying physical cleanup is handled entirely by Firefox, and you don’t need to intervene.

内容的提问来源于stack exchange，提问作者Olivier