mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #760] Floccus never propagates deletions, always adds them back in #482
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#482
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 @morgannunan on GitHub (Jan 1, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/760
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Expected behavior
The bookmark has been deleted on both sides. However, it hasn't, and when I go back to computer 1, the deleted bookmark is present again. This is especially messy when organizing bookmarks, because I'll move them to a subfolder and then they'lll be put back, so now I have the same bookmark in two places.
Desktop (please complete the following information):
Server (please complete the following information):
Debug log
When I click 'debug log', nothing happens.
@marcelklehr commented on GitHub (Jan 21, 2021):
Thank you for your feedback. The v4.4.x series has been rolled out now on the chrome webstore, which should fix this. If you continue to experience problems feel free to open a new issue. ❤️
@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.