mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #150] Bookmarks and folders re-arranged in Alphabetical Order - WebDAV/xbel #140
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#140
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 @darrellittle on GitHub (Aug 23, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/150
Software versions
Steps to reproduce
Expected/Actual outcome
I was hoping the bookmarks and folders would keep the same order as the initial synced browser's bookmarks, but everything was rearranged into alphabetical order, including bookmarks and folders in all subfolders.
Is there a way to have the bookmarks appear in a custom order as opposed to alphabetical, and have that carry over to all browsers? By custom, I mean arrange the bookmarks in either Chrome or Firefox the way I want, and then do the initial sync using Nextcloud and WebDAV.
Thanks
@marcelklehr commented on GitHub (Aug 24, 2018):
Hey there,
That's currently not implemented. It is however possible with the WebDAV/XBEL adapter.
As this has been requested before, I'm closing this as a duplicate of #113
@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.