mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #1015] Tab sync fails #667
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#667
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 @sevmonster on GitHub (Dec 31, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1015
Describe the bug
I have a Nextcloud account set up for tab sync in the Chrome extension. One of the reasons I decided on this solution was explicitly for tab sync, so I could easily merge session management and bookmarks into a single flow; I like being able to drag tabs over to bookmarks easily and selectively, especially without having the device in question in front of me. However, it isn't working as I expected. Pulling changes from the server results in errors if they were not initially pushed by floccus.
To Reproduce
Enable tab sync and create a new bookmark or folder in Nextcloud under the tab sync folder.
Expected behavior
The newly created bookmarks are opened in the browser.
Desktop
Server
Debug log
I get this error when floccus attempts to create tabs:
Creating a new folder anywhere results in this:
Additional context
With the account set to always replace upstream changes, there are no problems. If pulling in sync tabs mode isn't properly functional or supported, it should probably be disabled in the UI and disabled in existing account settings?
@github-actions[bot] commented on GitHub (Dec 31, 2021):
Hi @sevmonster! This issue is being automatically closed because it does not follow the issue template.
@candrapersada commented on GitHub (Feb 10, 2022):
Browser
@sevmonster commented on GitHub (Feb 11, 2022):
Thank you!
@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.