Version: 1.7.8 (patch) Date: 2025-10-15 Summary This patch fixes a critical startup-sync bug that could remove user containers when the extension performed an automatic sync at browser startup. It adds multiple safety checks and improved handling around Airtable fetches and the container cleanup logic. It also preserves active and system containers and significantly improves logging to help diagnose sync problems. Highlights

Prevent mass-deletion of containers when Airtable responses are empty or fail.
Protect containers currently in use (containers with open tabs) from deletion.
Exclude Firefox system containers (e.g. default and private) from any deletion attempts.
Improve Airtable fetch error handling and add safety checks (abort sync on suspicious/empty responses).
Add more granular logging to aid debugging and production troubleshooting.

Files changed

background.js — main changes:
Added safety checks before cleanup (abort if Airtable records are empty or invalid).
Improved error handling for Airtable fetch (check HTTP status, surface API errors).
Added cache-buster to Airtable fetch requests (already present, logging improved).
Filtered out Firefox system containers when enumerating existing containers.
Added detection of active containers (via tabs) and skip deletion for those.
Added additional logging for counts and decision points during sync.
manifest.json — no behavioral change in this release (no new permissions or background mode changes).

Bug fixes

Fix: Containers could be deleted on browser startup if the Airtable fetch returned empty/invalid data or failed. Now the sync aborts safely in those scenarios.
Fix: System containers (e.g., firefox-default, firefox-private) were at risk of being processed — now explicitly excluded.
Fix: Containers that have open tabs are now protected from deletion during cleanup.

Behavior changes / Notes

Startup sync still runs on onStartup / onInstalled events (no periodic sync added).
The sync process is now conservative: if Airtable returns zero records or the request fails, the cleanup phase is aborted to avoid accidental deletions.
Logging verbosity for background sync has increased to assist debugging. This may be visible in the Browser Console during QA.

Autorisations nécessaires :