You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: pull-only sync should not push back to cloud — prevents ordering revert
The receiving browser (e.g. Chromium) was pushing bookmarks back to cloud
after pulling updates from the source browser (e.g. Firefox), overwriting
the source browser's ordering changes. This caused a revert cycle:
1. Firefox reorders → syncs to cloud ✅
2. Chromium syncs → pulls new order → but also pushes back with old indices
3. Firefox syncs → pulls Chromium's overwritten order → reverts
Root cause: bookmarksToUpdate (cloud→local updates) was incorrectly counted
as 'local changes to push'. And Step 9 always pushed regardless of whether
there were actual local changes.
Fix:
- Remove bookmarksToUpdate from hasLocalChangesToPush (they're cloud→local)
- Gate Step 9 push behind hasLocalChangesToPush check
- Store cloud checksum on pull-only syncs for future comparison
v0.8.19
0 commit comments