quirks

Known Quirks (verified — read before refactoring)

Extracted verbatim from AGENTS.md. The main file carries one-line summaries; this is the full text.

• Deletion undo lives in src/undo.js (P3.3): subtree snapshots in chrome.storage.session, restored depth-first; a failed restore consumes the stack entry without rollback of the partial result (by design). v4 task-2 slice A2 revived the confirmDeleteFolder* keys: deleting a non-empty folder is ConfirmDialog-gated again (default on via the confirmDeleteFolder setting, dialog copy notes the undo path; empty folders and bookmark rows still delete straight to the toast).
• Sync-status computation lives in the service worker (src/sync-engine.js, P3.6); pages only mirror the published blob. node.syncing requires Chrome 138+: on older Chrome the status is genuinely unknown and the engine reports '' — it never fabricates synced (the old page-side manager treated "URL is not chrome://" as synced, and its cache-write shapes never matched its cache reads). Since the 2026-08 perf audit the engine IDLES below Chrome 138 (no refresh alarm, no event-driven recomputes — a timed recompute could only re-derive "unknown"; only the page-driven vbm-sync-status-request/vbm-sync-refresh messages still compute, which preserves the unsyncable markers for blacklisted URL schemes), the alarm is additionally gated on showSyncStatus, the four id-bearing bookmark events are batched into one 300 ms-debounced id-Set pass, and the 500 ms flush skips unchanged republishes via a sorted-keys fingerprint that excludes ts. The Chrome-version probe is a minimal in-module Chrome/<major> UA parse with fail-open — no SW-side probe existed before. Tooltips are localized via chrome.i18n with inline English fallbacks (syncStatusSynced/syncStatusLocal/syncStatusUnsyncable); the old folderType (Synced) concatenation leaked raw enum values and is gone. chrome.alarms rejects periods below 0.5 minutes, so the syncRefreshInterval option floor is 30 s. highlightUnsynced (default on) is honored: syncing === false tree rows get the unsynced-subtree class and the whole local subtree renders dimmed under body.highlight-unsynced.
• Sync-preference keys live in chrome.storage.sync — since the 2026-08 storage audit that is ~45 small device-independent preferences (searchHistoryCount joined in the 2026-08-26 options round) (store.js SYNC_KEYS: the original showSyncStatus/highlightUnsynced/autoRefreshSync/syncRefreshInterval + paletteCustomCommands, theme/language, behavior toggles, view show/disable keys, feature switches, sort/filter prefs). Access is area-transparent: store.get/set and the getSetting/setSetting helpers route them automatically, localStorage doubles as their synchronous boot cache, and a one-time local→sync migration runs at store init. Bookmark-id-keyed data (quickAddFolderId, separators*, deadMarks*, visitStats) deliberately stays local — Chrome does not keep bookmark ids stable across devices; customIcon stays local because its serialized form (~10-14KB) exceeds the 8KB/item sync limit. Pages may still read the original four via store.getSyncSetting; both src/sync-engine.js and the options page normalize string and boolean forms.
• iGuge conflict (issues #53/#57): the store-shipped iGuge proxy/acceleration extension (CRX v2.3.9, ID ncldcbhpeplkfijdhnoepdgdnmjkckij) actively disables any enabled extension that declares the proxy permission and is not on its server-pushed whitelist proxy_permissions_namewhilelist (default ["IDM Integration Module"]) — its service worker's check_clash_app() calls chrome.management.setEnabled(id, false) at every startup (js/iggservice.js). vBookmarks holds install-time proxy (Chrome forbids it as optional) for the dead-link proxy channel, so whenever both are installed vBookmarks is re-disabled on every Chrome restart. Decision (2026-08): keep the feature and coordinate whitelisting with iGuge — do NOT remove the proxy permission (removing it is the only vBookmarks-side fix, at the cost of the dead-link proxy channel). Full verified analysis + iGuge outreach draft: docs/issues/issue-53-57-iguge-conflict.md.