mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #928] Tabs synced to NextCloud bookmarks have no names #598
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#598
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 @mnalis on GitHub (Aug 6, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/928
Is your feature request related to a problem? Please describe.
When I use
Sync tabsoption of floccus to sync tabs to Nextcloud Bookmarks app, they are uploaded, but without any names.Describe the solution you'd like
It would be nice if names of tabs would be retained when syncing.
Firefox show tabs names (as specified by
<title>HTML tag) in the tabs, so if that is available to extensions too, it would great to make it tab name when syncing to Nextcloud bookmarks. Or, if the title is unavailable, perhaps just the URL could be substituted as "bookmark name" of that tab too.Describe alternatives you've considered
Alternatively, synced tabs could be nameless, and Nextclould bookmarks app could be modified to show URL if the name is completely empty. (should open a new issue there, if preffered solution above is not possible)
Additional context
@github-actions[bot] commented on GitHub (Mar 20, 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.