mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #732] Order of bookmarks and folders differ in 4.4.6 and 4.3.0 #471
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#471
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 @bhlevca on GitHub (Nov 20, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/732
Describe the bug
Firefox is at 4.4.6 and Chrome is at v 4.3.0. Sync between them messes up the order of bookmarks an folders
To Reproduce
Steps to reproduce the behavior:
E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't exist E013: Folder to remove doesn't existHowever, when the sync is set to overwrite the locals there is no error and the order is fine.
Expected behavior
Same order of bookmarks
Desktop (please complete the following information):
@bhlevca commented on GitHub (Nov 20, 2020):
I guess the fact you can select the write over that works should be enough
@github-actions[bot] commented on GitHub (Mar 21, 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.