mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #884] Bookmarks order not preserved on initial unidirectional sync #572
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#572
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @deragon on GitHub (Jun 5, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/884
Describe the bug
Bookmarks order not preserved when syncing from Chrome to WebDAV to Firefox.
To Reproduce
Expected behavior
Under Firefox, I expect that the bookmarks are set in the same order as in Chrome, but this is not the case. The order seams random.
However, I do not believe any bookmark is missing. The problem is only with the order not being respected.
Desktop
Server
@marcelklehr commented on GitHub (Jun 10, 2021):
Thank you for the feedback and sorry for the trouble, I'm a bit swamped at the moment, but will look into this soon-ish.
@verglor commented on GitHub (Jun 12, 2021):
Hi, I have the same problem with Chrome -> Google Drive -> Firefox sync.
@marcelklehr commented on GitHub (Jul 14, 2021):
Confirmed. If you pull-sync a second time, the order is fixed. Note to self: This is a bug in the UnidirectionalMerge strategy.
@github-actions[bot] commented on GitHub (May 24, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.