mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #850] sync tabs when browser start #544
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#544
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 @candrapersada on GitHub (Mar 10, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/850
how to revert local changes and pull upstream remote changes at browser startup and Always revert upstream remote changes and push local changes every x minutes automatically for browser tabs?
@github-actions[bot] commented on GitHub (Mar 10, 2021):
Hi @candrapersada! This issue is being automatically closed because it does not follow the issue template.
@github-actions[bot] commented on GitHub (Mar 10, 2021):
Hi @candrapersada! This issue is being automatically closed because it does not follow the issue template.
@marcelklehr commented on GitHub (Mar 10, 2021):
@candrapersada Currently you'll have to manually pull upon opening the browser and set the sync strategy to push.
@candrapersada commented on GitHub (Mar 10, 2021):
what I mean is to use sync strategy automatically
@marcelklehr commented on GitHub (Mar 10, 2021):
I could add an option to only sync on browser start. Then you could have one account that regularly pushes and one that pulls once on startup.
@candrapersada commented on GitHub (Mar 12, 2021):
and i want to ask if the pull and push time can be adjusted so that there is no problem like tabs I have recently closed reappear through the sync quite often
@marcelklehr commented on GitHub (Mar 12, 2021):
If you're talking about the sync frequency, you can definitely adjust that.
@candrapersada commented on GitHub (Mar 13, 2021):
The time between two synchronizations runs in a few minutes. The default is 15 minutes. when the browser starts sync runs itself before 15 minutes

for example when I start the browser after 1 day close the sync starts immediately before 15 minutes why this happens?
@marcelklehr commented on GitHub (Jul 14, 2021):
This happens because the 15 minutes are calculated as the difference between current time and last sync time. If you haven't had the browser open for more than a day, that's more than 15min.
@marcelklehr commented on GitHub (Jul 14, 2021):
Fixed by
aca81a5065-- now it will sync automatically within 7s of opening the browser.@candrapersada commented on GitHub (Mar 12, 2022):
why until now there is still no feature
pull sync oncewhen starting browser andpush syncevery 15 minutes orauto disable syncwhen starting browserfloccus 4.11.0.1
based Chromium
@candrapersada commented on GitHub (Jun 22, 2024):
Why is the tab sync problem still not resolved?
@marcelklehr commented on GitHub (Jun 22, 2024):
Hey, I've been dealing with more pressing issues so far and was also not sure how to proceed as the requirement to be able to pull sync on browser start and push sync the rest of the time is radically different from the way bookmark sync is handled
@marcelklehr commented on GitHub (Nov 28, 2024):
I think the underlying problem behind your request is that merge sync doesn't work well with tabs, which you would want to use all the time, be it at browser start or during a browsing session. I've recently drastically improved merge sync for tabs, which should hopefully obviate the need for your intricate "strategy switching" request. I'll let you know once the release is published. :)
@github-actions[bot] commented on GitHub (Dec 22, 2025):
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.