mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1297] Refresh is triggered to easily and quickly #861
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#861
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 @godfuture on GitHub (Nov 25, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1297
Which version of floccus are you using?
4.17.1
Sync method
Nextcloud Bookmarks
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Android 12 on Fairphone 3+ Witz lineageOS 19.1
Which version of Nextcloud Bookmarks are you using? (if relevant)
currently latest
Which version of Nextcloud? (if relevant)
24.0.7
What kind of WebDAV server are you using? (if relevant)
Nextcloud 24 with booksmarks app.
Describe the Bug
Scrolling up triggers the sync too easy. Mostly I hit the refresh even though I just wanted to scroll up.
Expected Behavior
The UI should less sensitive to pull down when scrolling. The user should have a good control when to refresh and when not while scrolling the screen. Therefore it needs a certain area of tolerance where the user has to "overscroll" to make the refresh trigger.
To Reproduce
Connect to server
Wait for first sync
Scroll till bottom
Try to scroll till top without triggering refresh
Debug log provided
@marcelklehr commented on GitHub (Nov 26, 2022):
I tend to agree. It would be a nice feature, but implemented like this it's not cool
@godfuture commented on GitHub (Nov 27, 2022):
Exactly. Also for users with extend bookmark db size, the sync takes longer. In my case for internal LAN it only syncs with 2 MBits. Dont know why, but somehow there is a bottleneck. If I accidently hit refresh, I always have to wait for sync to finish.
Thanks for your quick help here.
@github-actions[bot] commented on GitHub (Nov 28, 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.