mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #831] Built-in node"Mobile bookmarks" not syncing between Chrome and Firefox #531
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#531
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 @lkmill on GitHub (Feb 11, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/831
Describe the bug
If you set the local folder to the root folder, the "Mobile bookmarks" folder does not sync between Firefox and Chrome.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Mobile Bookmarks should be copied.
I know i could set this up via https://github.com/marcelklehr/floccus#the-server-path-mapping-folders--profiles, but would be nice if it worked syncing the root folder.
I presume some fiddling in
github.com/marcelklehr/floccus@c9d4d8fffc/src/lib/LocalTree.ts (L36-L49)would enable this feature.Screenshots
If applicable, add screenshots to help explain your problem.
Desktop
(please complete the following information)
Server
(please complete the following information)
Note: Please write down the actual version numbers instead of writing 'latest'.
Debug log
It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser.
Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://cloud.marcelklehr.de/s/PCi3iLWrzdMZSmw
Additional context
Add any other context about the problem here.
@marcelklehr commented on GitHub (Feb 12, 2021):
Mmmh, does Chrome have a Mobile Bookmarks folder built-in?
@lkmill commented on GitHub (Feb 12, 2021):
@marcelklehr yes, it works the same way as the firefox built-in folder. ie if you press the bookmark button in mobile chrome (both iOS and android), the bookmark is added to the "Mobile bookmarks" folder
@lkmill commented on GitHub (Feb 12, 2021):
i forgot to mention in the bug report, it also appears if you create folders in your Firefox "Mobile bookmarks" floccus will error when syncing in Chrome saying the parent folder does not exist.
@lkmill commented on GitHub (Feb 27, 2021):
@marcelklehr saw you reopened and closed one of my attempts at posting this issue that did not follow the issue template properly... did you mean to close this one?
@marcelklehr commented on GitHub (Feb 27, 2021):
Nope, sorry, I thought there was no open version of this issue, but overlooked this one. :)
@marcelklehr commented on GitHub (Mar 15, 2021):
@lohfu, the problem is that the mobile folder only exists when having used the built-in browser sync. In firefox it seems the mobile bookmarks folder has a constant ID, but in chrome the that doesn't seem to be the case :/
@lkmill commented on GitHub (Mar 16, 2021):
ah. is the name "Mobile bookmarks" combined with the fact that the parent dir is the root not enough of an identifier?
@marcelklehr commented on GitHub (Mar 16, 2021):
Probably not as the names of the built-in folders are localized :/
@lkmill commented on GitHub (Mar 16, 2021):
well that's a bummer
@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.