mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #132] Bookmarks with no name are renamed to the server's <title> and are reordered as the last bookmarks #121
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#121
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 @synthead on GitHub (Jul 10, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/132
Software versions
Steps to reproduce
<title>and that the bookmark has been reordered as the last bookmark.Expected outcome
The bookmark names and ordering in FireFox should remain as-is, and a bookmark with no name should be synced to the Bookmarks app in Nextcloud via Floccus
Actual outcome
Bookmarks with no names were given a name of the server's
<title>and are reordered as the last bookmarks.@marcelklehr commented on GitHub (Jul 16, 2018):
The reordering is to be expected as the nextcloud app doesn't allow ordering bookmarks.
The title change is unfortunate. I'll see what I can do...
@marcelklehr commented on GitHub (Jul 28, 2018):
This should be fixed in v3.0.0. Please test the beta version to confirm: #131 :)
@marcelklehr commented on GitHub (Aug 3, 2018):
Will be fixed in the next beta release of v3
@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.